Autonomous transaction

From: Loïc Vaumerel <shefla(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Autonomous transaction
Date: 2010-04-04 14:26:53
Message-ID: l2t5d2f25dc1004040726ica3a38d8x70c1685d2b096a7a@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

I have an application project based on a database.
I am really interested in using PostgreSQL.

I have only one issue, I want to use autonomous transactions to put in place
a debug / logging functionality.
To do so, I insert messages in a "debug" table.
The problem is, if the main transaction / process rollback, my debug message
insert will be rolled back too.
This is not the behavior I wish.

I need a functionality with the same behavior than the Oracle "PRAGMA
AUTONOMOUS_TRANSACTION" one.
I have searched for it in the documentation and on the net, unfortunately
nothing. (maybe I missed something)

I just found some posts regarding this :
http://archives.postgresql.org/pgsql-hackers/2008-01/msg00893.php
https://labs.omniti.com/trac/pgtreats/browser/trunk/autonomous_logging_tool
... and some others ...

All solutions I found are working the same way : they use dblink.
I consider these solution more as handiwork than a clean solution.
I am a little bit concerned about side effects as dblink were not intially
designed for this.

So my questions :
Is there a way to use real and clean autonomous transactions in PostgreSQL
yet ?
If no, is it planned to do so ? When ?

Thanks in advance

Best regards

Shefla

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-04-04 15:57:28 Re: "pg_stat_tmp/pgstat.stat": Stale NFS file handle
Previous Message Hitoshi Harada 2010-04-04 07:59:30 make check hangs in alpha5