Re: BUG #17068: Incorrect ordering of a particular row.

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, ganeshmmahesh(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #17068: Incorrect ordering of a particular row.
Date: 2021-06-22 14:19:23
Message-ID: CAApHDvryiB2GS8ApTkcUhw34Ats7+o-wCutz9jO3vFuRQ-XgAg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, 23 Jun 2021 at 02:00, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> (I'd suspected something of the kind, but being caffeine-deprived I'd
> first added "alias3.* IS NULL" to the query, which of course fails to
> expose the difference. Thanks SQL.)
>
> In short, I see no bug here. It is kind of obscure though.

Oh right. Thanks for looking.

David

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2021-06-22 15:10:42 Re: BUG #17062: Assert failed in RemoveRoleFromObjectPolicy() on DROP OWNED policy applied to duplicate role
Previous Message Tom Lane 2021-06-22 14:11:06 Re: BUG #17064: Parallel VACUUM operations cause the error "global/pg_filenode.map contains incorrect checksum"