From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: bokanist@gmail.com
Subject: BUG #17840: Failing to execute auto_explain for logging leads to transaction rollback.
Date: Tue, 14 Mar 2023 11:18:47 +0000
Message-ID: <17840-c480ed3600feea0e@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 17840
Logged by: Sebastien Caunes
Email address: bokanist@gmail.com
PostgreSQL version: 13.2
Operating system: Linux
Description:
I had this problem when importing data from oracle with oracle_fdw and
auto_explain option set on the postgres server : If the query took too long,
it triggers the auto_explain wich queries things on oracle side where there
was a permission problem. The error bubble up outside of logging scope and
make the transaction rollback after having properly transferred dozen
million records (that then stood as dead tuples).
Logging is one thing with its own scope and it should never interfere with
the behavior of the software. Beside whatever reason triggering the error in
logging scope, the transaction that had no problem itself should not be
rollbacked. It makes no sense.
Isn't there something to refactor in Postgres ?
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: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, bokanist@gmail.com
Subject: Re: BUG #17840: Failing to execute auto_explain for logging leads to transaction rollback.
In-Reply-To: <17840-c480ed3600feea0e@postgresql.org>
* 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