Re: [HACKERS] Statement Triggers. Ideas & help.

From: Vadim Mikheev <vadim(at)krs(dot)ru>
To: F J Cuberos <fjcuberos(at)infomail(dot)lacaixa(dot)es>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Statement Triggers. Ideas & help.
Date: 1999-08-17 01:55:27
Message-ID: 37B8C10F.8AAD4608@krs.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

F J Cuberos wrote:
>
> Forget the problem with Executeplan, I was getting the syslogs and stdour
> messages in the same screen; SO DOUBLE!!!!.
>
> With statement triggers (and defined in SQL3 too) will be interesting to
> access OLD and NEW values of modified tables. How can be implemented? It´s
> possible to use MVCC for this?

MVCC uses t_xmin/t_xmax to decide what's visible to transaction.
For OLD/NEW you will have to analyze t_cmin/t_cmax as well.

Vadim

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1999-08-17 01:55:36 Re: [HACKERS] Re: [CORE] Re: tomorrow
Previous Message Vince Vielhaber 1999-08-17 01:43:05 Re: [HACKERS] Re: [CORE] Re: tomorrow