From: Tom Lane <tgl@sss.pgh.pa.us>
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: julius.ernesti@kpi4me.de <julius.ernesti@kpi4me.de>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #18457: Possible data loss needs to be evaluated
Date: Tue, 07 May 2024 09:58:15 -0400
Message-ID: <4056218.1715090295@sss.pgh.pa.us> (raw)
In-Reply-To: <CAKFQuwaafYfpNTF0G+M47JnpnG-Wa3xAsbH+k0WM5LRX8NUucw@mail.gmail.com>
References: <18457-dc62fafe74c67bdd@postgresql.org>
<CAKFQuwaafYfpNTF0G+M47JnpnG-Wa3xAsbH+k0WM5LRX8NUucw@mail.gmail.com>
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> If you actually perform that algorithm manually using two psql sessions you
> will find, if done properly, that the row with id=4 exists. If it does not
> then show that work because you will indeed have found a bug. But as of
> now you have not demonstrated a bug in PostgreSQL.
Yeah. This could be a Postgres problem, or it could be an application
problem. Given the lack of other similar reports, the a-priori
assumption has to be that it's an application problem. In any case,
there's no way for the rest of us to investigate since we don't have
access to either the application or data involved.
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, david.g.johnston@gmail.com, julius.ernesti@kpi4me.de, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18457: Possible data loss needs to be evaluated
In-Reply-To: <4056218.1715090295@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