|From:||David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>|
|To:||Andres Freund <andres(at)anarazel(dot)de>|
|Cc:||Amit Langote <amitlangote09(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: [HACKERS] path toward faster partition pruning|
|Views:||Raw Message | Whole Thread | Download mbox|
On 7 April 2018 at 15:00, Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2018-04-07 14:42:53 +1200, David Rowley wrote:
>> On 7 April 2018 at 13:31, David Rowley <david(dot)rowley(at)2ndquadrant(dot)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
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.
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
|Next Message||David Rowley||2018-04-07 03:07:28||Re: [HACKERS] path toward faster partition pruning|
|Previous Message||Ashutosh Bapat||2018-04-07 03:03:06||Re: [HACKERS] path toward faster partition pruning|