Re: commit callback, request

From: "Pavel Stehule" <pavel(dot)stehule(at)hotmail(dot)com>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: commit callback, request
Date: 2006-04-05 14:44:12
Message-ID: BAY20-F12BC2EEC698F010D577725F9CB0@phx.gbl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>"Pavel Stehule" <pavel(dot)stehule(at)hotmail(dot)com> writes:
> > Is possible make transaction commit trigger without patching code now?
>
>You can get pretty close with a deferred trigger. I don't think
>there's any way to have a guaranteed "at commit" trigger --- as soon
>as (1) there are two of them and (2) one can get an error, the
>transaction could fail after running an alleged "at commit" trigger.
>
> regards, tom lane

hm. I don't have big problem with false notifications. Who want to use
dbms_alert have to calculate with this possibility. But triggers has
disadventage - I have to sometimes clean any table, which cary triggers :-(.
It's solution. I hope 8.2 will has any general mechanis. Is it possible
enhance SPI to parametrized NOTIFY? Default mode send message via libpq,
nonstandard raise any callback.

Thank You
Pavel

_________________________________________________________________
Citite se osamele? Poznejte nekoho vyjmecneho diky Match.com.
http://www.msn.cz/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2006-04-05 14:45:00 Re: Stats collection on Windows
Previous Message Magnus Hagander 2006-04-05 14:42:40 Re: Stats collection on Windows