On 7 April 2018 at 15:00, Andres Freund <and...@anarazel.de> wrote: > On 2018-04-07 14:42:53 +1200, David Rowley wrote: >> On 7 April 2018 at 13:31, David Rowley <david.row...@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. -- David Rowley http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
0002-Add-HASH-partition-pruning-tests.patch
Description: Binary data
