From: Noah Misch <noah@leadboat.com>
To: Дмитрий Секретов <d.sekretov@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17070: Sometimes copy from ingnores transaction
Date: Fri, 17 Sep 2021 20:18:49 -0700
Message-ID: <20210918031849.GA2911957@rfd.leadboat.com> (raw)
In-Reply-To: <CABarshpjx=o3FiJuYi0QJrVbhGzDxM0MsO6_5dpnJNHa8NwdEw@mail.gmail.com>
References: <17070-701777d014fe5684@postgresql.org>
<20210822183849.GA1747628@rfd.leadboat.com>
<CABarshpjx=o3FiJuYi0QJrVbhGzDxM0MsO6_5dpnJNHa8NwdEw@mail.gmail.com>
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.
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: noah@leadboat.com, d.sekretov@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17070: Sometimes copy from ingnores transaction
In-Reply-To: <20210918031849.GA2911957@rfd.leadboat.com>
* 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