| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | ishasonal1841(at)yahoo(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16535: Implementing Autonomous Transactions in Postgresql |
| Date: | 2020-07-10 21:40:32 |
| Message-ID: | 3206B98F-1B19-4E1A-A823-D84CA5FF6F25@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> On Jul 10, 2020, at 14:30, PG Bug reporting form <noreply(at)postgresql(dot)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(at)thebuild(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2020-07-10 21:44:31 | Re: BUG #16535: Implementing Autonomous Transactions in Postgresql |
| Previous Message | PG Bug reporting form | 2020-07-10 21:30:14 | BUG #16535: Implementing Autonomous Transactions in Postgresql |