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>,
        "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #18457: Possible data loss needs to be evaluated
In-reply-to: 
 <CAKFQuwaafYfpNTF0G+M47JnpnG-Wa3xAsbH+k0WM5LRX8NUucw@mail.gmail.com>
References: <18457-dc62fafe74c67bdd@postgresql.org>
 <CAKFQuwaafYfpNTF0G+M47JnpnG-Wa3xAsbH+k0WM5LRX8NUucw@mail.gmail.com>
Comments: In-reply-to "David G. Johnston" <david.g.johnston@gmail.com>
	message dated "Tue, 07 May 2024 05:20:38 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4056217.1715090295.1@sss.pgh.pa.us>
Date: Tue, 07 May 2024 09:58:15 -0400
Message-ID: <4056218.1715090295@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/4056218.1715090295%40sss.pgh.pa.us>
Precedence: bulk

"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