Re: [HACKERS] path toward faster partition pruning
От | Andres Freund |
---|---|
Тема | Re: [HACKERS] path toward faster partition pruning |
Дата | |
Msg-id | 20180407031841.wew4h7d5bjzekrpc@alap3.anarazel.de обсуждение исходный текст |
Ответ на | Re: [HACKERS] path toward faster partition pruning (David Rowley <david.rowley@2ndquadrant.com>) |
Ответы |
Re: [HACKERS] path toward faster partition pruning
Re: [HACKERS] path toward faster partition pruning |
Список | pgsql-hackers |
On 2018-04-07 15:04:37 +1200, David Rowley wrote: > On 7 April 2018 at 15:00, Andres Freund <andres@anarazel.de> wrote: > > On 2018-04-07 14:42:53 +1200, David Rowley wrote: > >> On 7 April 2018 at 13:31, David Rowley <david.rowley@2ndquadrant.com> wrote: > >> > Maybe the best solution is to pull those tests out of > >> > partition_prune.sql then create partition_prune_hash and just have an > >> > alternative .out file with the partitions which match on bigendian > >> > machines. > >> > >> Here's 1 of 2. I thought it was best to get the buildfarm green again > >> as soon as possible. > > > > Do you have an estimate how long it'll take you to produce patch 2? It'd > > be cool to get this covered again soon. If you don't have access to a > > big endian machine, we can construct the output from the buildfarm... So > > pulling the tests out would be the only "urgent" thing, I can go on from > > there. > > Attached. > > I've not tested on a bigendian machine, but the diff -c between the > two output files match the diff on the failing buildfarm members. I've pushed the two patches (collapsed). Trying to get the BF green-ish again... - Andres
В списке pgsql-hackers по дате отправления: