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

From: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
To: Vadim Mikheev <vadim(at)krs(dot)ru>, 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 05:29:47
Message-ID: 3.0.5.32.19990817152947.00b36920@mail.rhyme.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At 09:55 17/08/99 +0800, Vadim Mikheev wrote:
>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.

FWIW, Dec (Oracle) Rdb does not allow access to OLD & NEW in statement
triggers; if you want the rows, you have to write 'for each row' triggers.

----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.C.N. 008 659 498) | /(@) ______---_
Tel: +61-03-5367 7422 | _________ \
Fax: +61-03-5367 7430 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Lockhart 1999-08-17 06:11:49 Re: [HACKERS] Re: [CORE] Re: tomorrow
Previous Message Bruce Momjian 1999-08-17 03:57:32 Re: [HACKERS] Re: [CORE] Re: tomorrow