From: Tom Lane <tgl@sss.pgh.pa.us>
To: Joakim Goldkuhl <joakim.goldkuhl@cogmed.com>
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17925: Incorrect select query result
In-reply-to: 
 <CABrXk-Kg61o5hXq1Xjf+t=nZXC-Sgr9CQKG+ZHDaYOE-0qC2kQ@mail.gmail.com>
References: <17925-11423596f9c67cb8@postgresql.org>
 <455351.1683574146@sss.pgh.pa.us>
 <CABrXk-Kg61o5hXq1Xjf+t=nZXC-Sgr9CQKG+ZHDaYOE-0qC2kQ@mail.gmail.com>
Comments: In-reply-to Joakim Goldkuhl <joakim.goldkuhl@cogmed.com>
	message dated "Tue, 09 May 2023 09:00:22 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <670418.1683640643.1@sss.pgh.pa.us>
Date: Tue, 09 May 2023 09:57:23 -0400
Message-ID: <670419.1683640643@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/670419.1683640643%40sss.pgh.pa.us>
Precedence: bulk

Joakim Goldkuhl <joakim.goldkuhl@cogmed.com> writes:
> Since this is corporation data I cannot provide much data in this public
> mailing list unfortunately. And I have not yet been able to reproduce this
> behaviour on dummy data.

Hm, well, please keep trying.

> Also, I should mention that the database is running on RDS, managed by AWS,
> so maybe you are not interested in looking into it in this case?

That does complicate matters, since it's hard to guess whether it's
a native Postgres bug or something Amazon introduced.  (I believe
RDS Postgres is mostly Postgres, unlike say Aurora, but there is some
secret sauce at the storage level.)  All the more reason to try to
devise a publishable test case.

			regards, tom lane