Access to transaction status

From: "Christian Plattner" <plattner(at)inf(dot)ethz(dot)ch>
To: <pgsql-hackers(at)postgresql(dot)org>
Subject: Access to transaction status
Date: 2003-06-19 15:11:00
Message-ID: 012b01c33674$fdfda2b0$6e828481@ethz.ch
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi all,

I am currently implementing an experimental middleware based replicator for
a set
of fully replicated databases.

Do be able to handle all sorts of failures I needed two functions:

- A function to get the current XID
- A function which I can use later to tell if a given XID
commited/aborted/whatever

I did a small implementation of this (see attachment).

Could one of you hackers tell me if you think this is

- an ugly way of accessing the clog?
- totally wrong because I missed some point?
- or a good and correct idea :)

It would be very nice if someone had the time to have a short look into
this.

Greetings,
Christian

Attachment Content-Type Size
postgres_xid_func.c application/octet-stream 1.9 KB

Browse pgsql-hackers by date

  From Date Subject
Next Message Christian Plattner 2003-06-19 15:16:10 Access to transaction status
Previous Message Tom Lane 2003-06-19 15:00:23 Re: add column .. default