Dealing with prepared transactions in XactCallback

From: Boszormenyi Zoltan <zb(at)cybertec(dot)at>
To: pgsql-general(at)postgresql(dot)org
Subject: Dealing with prepared transactions in XactCallback
Date: 2010-06-29 07:33:25
Message-ID: 4C29A1C5.1080904@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

I need to rework a custom notification scheme that sends TCP
messages about new/modified/deleted records to an external process.
It's obvious that I am using RegisterXactCallback() to do that.
The problem is with prepared transactions. I get XACT_EVENT_PREPARE
in the XactCallback function, where I can save the data to be sent later.
But how can I decide in a later transaction that the application
is doing COMMIT PREPARED for a particular Xid? Does PREPARE
TRANSACTION saves the TopTransactionContext and loads it back fully
so I don't need to worry about saving and reloading?

Thanks in advance,
Zoltán Böszörményi

Browse pgsql-general by date

  From Date Subject
Next Message dario.ber@libero.it 2010-06-29 07:37:36 R: Re: postgres user password: Log on failure
Previous Message Thomas Kellerer 2010-06-29 06:20:11 owner of a database does not own "public" schema?