Re: BUG #16535: Implementing Autonomous Transactions in Postgresql - Mailing list pgsql-bugs

From Christophe Pettus
Subject Re: BUG #16535: Implementing Autonomous Transactions in Postgresql
Date
Msg-id 3206B98F-1B19-4E1A-A823-D84CA5FF6F25@thebuild.com
Whole thread Raw
In response to BUG #16535: Implementing Autonomous Transactions in Postgresql  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs

> 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
applicationworkload and one specifically for logging and auditing, so that rollbacks or errors on the primary
connectiondo not affect the logging connection. 

--
-- Christophe Pettus
   xof@thebuild.com




pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #16535: Implementing Autonomous Transactions in Postgresql
Next
From: "David G. Johnston"
Date:
Subject: Re: BUG #16535: Implementing Autonomous Transactions in Postgresql