Re: BUG #19036: Failed prepared INSERT statement make another SELECT query generate wrong result

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: ZhangChi <798604270(at)qq(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #19036: Failed prepared INSERT statement make another SELECT query generate wrong result
Date: 2025-08-30 01:57:05
Message-ID: CAKFQuwZdRbac7ajisTqDSJp7Djj4EQCBJDkNb7de10nYd4gBrQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Friday, August 29, 2025, ZhangChi <798604270(at)qq(dot)com> wrote:
>
>
> I still have a problem with this. When an INSERT fails, why not undo all
> the effects of the INSERT?
>

Performance.

Sequences don’t go backward.

David J.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2025-08-30 02:06:32 Re: BUG #19036: Failed prepared INSERT statement make another SELECT query generate wrong result
Previous Message ZhangChi 2025-08-30 01:51:46 Re: BUG #19036: Failed prepared INSERT statement make another SELECT query generate wrong result