On Fri, 2010-12-03 at 12:26 -0500, Christopher Browne wrote:
> === Commit timestamps ===
> * per Jan Wieck
> * Requires PostgreSQL extension
> * Eliminates need for periodic generation of SYNC events
> * Simplifies queries for searching for sl_log_* data
> * Enables carryover of commit times to subscribers

It should be possible to do this using LISTEN/NOTIFY.
Now we can pass a payload with the NOTIFY, we just need to pass the
transaction id. That can be handled automatically by trigger.

What we need is commit order, not commit timestamp, yes?
NOTIFY happens in commit sequence. It doesn't provide the commit
timestamp, but perhaps that can be provided by the LISTENer, if you
really need it.

-- 
 Simon Riggs           http://www.2ndQuadrant.com/books/
 PostgreSQL Development, 24x7 Support, Training and Services