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
Date: Tue, 09 May 2023 09:57:23 -0400
Message-ID: <670419.1683640643@sss.pgh.pa.us> (raw)
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>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, joakim.goldkuhl@cogmed.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17925: Incorrect select query result
In-Reply-To: <670419.1683640643@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox