BUG #16535: Implementing Autonomous Transactions in Postgresql

Started by PG Bug reporting formalmost 6 years ago5 messagesbugs
Jump to latest
#1PG Bug reporting form
noreply@postgresql.org

The following bug has been logged on the website:

Bug reference: 16535
Logged by: Isha Sonal
Email address: ishasonal1841@yahoo.com
PostgreSQL version: 11.0
Operating system: unix
Description:

I am trying to enable logging / auditing / progress tracking feature even if
my all transactions are rollbacked back. I tried to handle it with
procedures but its not working. Please suggest how can i achieve this
feature in PostgreSQL 11.

I am currently working on Oracle DB and using Autonomous Transactions to
enable logging feature.

#2Christophe Pettus
xof@thebuild.com
In reply to: PG Bug reporting form (#1)
Re: BUG #16535: Implementing Autonomous Transactions in Postgresql

On Jul 10, 2020, at 14:30, PG Bug reporting form <noreply@postgresql.org> wrote:

I am trying to enable logging / auditing / progress tracking feature even if
my all transactions are rollbacked back. I tried to handle it with
procedures but its not working. Please suggest how can i achieve this
feature in PostgreSQL 11.

The most straight-forward method might be to establish two separate connections to the database, one for the primary application workload and one specifically for logging and auditing, so that rollbacks or errors on the primary connection do not affect the logging connection.

--
-- Christophe Pettus
xof@thebuild.com

#3David G. Johnston
david.g.johnston@gmail.com
In reply to: PG Bug reporting form (#1)
Re: BUG #16535: Implementing Autonomous Transactions in Postgresql

On Fri, Jul 10, 2020 at 2:39 PM PG Bug reporting form <
noreply@postgresql.org> wrote:

The following bug has been logged on the website:

Bug reference: 16535
Logged by: Isha Sonal
Email address: ishasonal1841@yahoo.com
PostgreSQL version: 11.0
Operating system: unix
Description:

Not really a bug report, questions like this are better directed to the
-general list.

I am trying to enable logging / auditing / progress tracking feature even
if
my all transactions are rollbacked back. I tried to handle it with
procedures but its not working. Please suggest how can i achieve this
feature in PostgreSQL 11.

I've seen dblink recommended for this purpose. In short you break out of
the transaction by opening a new connection to the current database from
inside the database and do your non-transactional work on it.

https://www.postgresql.org/docs/11/dblink.html

David J.

#4Konstantin Knizhnik
k.knizhnik@postgrespro.ru
In reply to: PG Bug reporting form (#1)
Re: BUG #16535: Implementing Autonomous Transactions in Postgresql

On 11.07.2020 00:30, PG Bug reporting form wrote:

The following bug has been logged on the website:

Bug reference: 16535
Logged by: Isha Sonal
Email address: ishasonal1841@yahoo.com
PostgreSQL version: 11.0
Operating system: unix
Description:

I am trying to enable logging / auditing / progress tracking feature even if
my all transactions are rollbacked back. I tried to handle it with
procedures but its not working. Please suggest how can i achieve this
feature in PostgreSQL 11.

I am currently working on Oracle DB and using Autonomous Transactions to
enable logging feature.

Autonomous transactions are supported in PgPro-EE (Postgres Professional
clone of Postgres).
In vanilla autonomous transaction can be simulated using dblink -
extension providing connections to PostgreSQL database from within a
database session.

#5legrand legrand
legrand_legrand@hotmail.com
In reply to: PG Bug reporting form (#1)
Re: BUG #16535: Implementing Autonomous Transactions in Postgresql

Hello,
There is pg_background extension at github that may suit your needs.

Regards
PAscal

--
Sent from: https://www.postgresql-archive.org/PostgreSQL-bugs-f2117394.html