From: | Kevin Field <kev(at)brantaero(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Transaction callback |
Date: | 2007-01-16 00:42:07 |
Message-ID: | 45AC1F5F.5040006@brantaero.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
http://archives.postgresql.org/pgsql-hackers/2004-01/msg00861.php
(Just to dredge up another old thread...)
> While its true that a post-commit operation cannot modify a database, it
> might still for instance propagate the outcome of the transaction to another
> resource outside of the database, it might invalidate a transaction local
> in-memory cache, or it might clear resources occupied in memory for a rule
> system, etc.
This is exactly what I'd like to do. Is there a way to do it nowadays?
What I'm going for is an AJAX app that doesn't need to poll the
server, but rather can have the server callback to it when a transaction
messes with the data a user at which a user is looking.
Any advice would be much appreciated.
Thanks,
Kev
From | Date | Subject | |
---|---|---|---|
Next Message | carter ck | 2007-01-16 00:44:57 | Improve Postgres Query Speed |
Previous Message | Steve Martin | 2007-01-15 23:51:52 | Re: PQexec does not return. |