| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Melanie Plageman <melanieplageman(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PGOPTIONS="-fh" make check gets stuck since Postgres 11 |
| Date: | 2019-07-10 07:21:28 |
| Message-ID: | CAA4eK1KSdx81WZpEUsaVfVfuqavLxEMQZyHQ3gQ-ErKduRY89A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jul 10, 2019 at 10:12 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Tue, Jul 09, 2019 at 11:54:29AM -0700, Melanie Plageman wrote:
> > It might be worth post-processing results files to ignore row ordering
> > in some cases to allow for easier comparison. Has this been proposed
> > in the past?
>
> Not that I recall.
>
It would be good if we can come up with something like that. It will
be helpful for zheap, where in some cases we get different row
ordering due to in-place updates. As of now, we try to add Order By
or do some extra magic to get consistent row ordering.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-07-10 07:28:04 | Re: Two pg_rewind patches (auto generate recovery conf and ensure clean shutdown) |
| Previous Message | Kyotaro Horiguchi | 2019-07-10 07:17:35 | make -jn fails by requiring not-yet-generated include files. |