From: Tom Lane <tgl@sss.pgh.pa.us>
To: bokanist@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17840: Failing to execute auto_explain for logging leads to transaction rollback.
Date: Tue, 14 Mar 2023 10:10:48 -0400
Message-ID: <2558506.1678803048@sss.pgh.pa.us> (raw)
In-Reply-To: <17840-c480ed3600feea0e@postgresql.org>
References: <17840-c480ed3600feea0e@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> 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 ?
This bug report is not actionable due to complete lack of specifics.
Please read
https://wiki.postgresql.org/wiki/Guide_to_reporting_problems
Having said that, my guess is that if there's anything to be done
it would need to be done in oracle_fdw. So you need to take this
up with the oracle_fdw authors, not here which is for core-server
problem reports.
regards, tom lane
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: tgl@sss.pgh.pa.us, bokanist@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17840: Failing to execute auto_explain for logging leads to transaction rollback.
In-Reply-To: <2558506.1678803048@sss.pgh.pa.us>
* 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