From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | ishasonal1841(at)yahoo(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #16535: Implementing Autonomous Transactions in Postgresql |
Date: | 2020-07-10 21:44:31 |
Message-ID: | CAKFQuwaAk7=9jbfAZTUL0_2UD_fACHTcUz+foPym2wr-CnnkLA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Fri, Jul 10, 2020 at 2:39 PM PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 16535
> Logged by: Isha Sonal
> Email address: ishasonal1841(at)yahoo(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Konstantin Knizhnik | 2020-07-11 07:12:11 | Re: BUG #16535: Implementing Autonomous Transactions in Postgresql |
Previous Message | Christophe Pettus | 2020-07-10 21:40:32 | Re: BUG #16535: Implementing Autonomous Transactions in Postgresql |