Re: BUG #17070: Sometimes copy from ingnores transaction - Mailing list pgsql-bugs

From Noah Misch
Subject Re: BUG #17070: Sometimes copy from ingnores transaction
Date
Msg-id 20210918031849.GA2911957@rfd.leadboat.com
Whole thread Raw
In response to Re: BUG #17070: Sometimes copy from ingnores transaction  (Дмитрий Секретов <d.sekretov@gmail.com>)
List pgsql-bugs
On Fri, Sep 17, 2021 at 02:13:43PM +0300, Дмитрий Секретов wrote:
> It happens very rarely and it happens in production (2-3 times a year), i
> can't log all. I look into code and we always start transaction. We have
> tests - rollback works fine. But it happened.

A missing BEGIN is something like one hundred times as likely as a PostgreSQL
bug here.  I understand you can't set log_statement=all in production.  If you
do a non-production test with log_statement=all, you may be able to locate the
missing BEGIN.



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #17194: Issue with pgoutput
Next
From: Jaime Casanova
Date:
Subject: Re: BUG #17061: Impossible to query the fields of the tuple created by SEARCH BREADTH FIRST BY .. SET ..