Re: Triggered Data Change check - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Triggered Data Change check
Date
Msg-id 623.1005534686@sss.pgh.pa.us
Whole thread Raw
In response to Re: Triggered Data Change check  (Hiroshi Inoue <Inoue@tpf.co.jp>)
Responses Re: Triggered Data Change check
List pgsql-hackers
Hiroshi Inoue <Inoue@tpf.co.jp> writes:
> Strictly speaking MVCC is only for read-only queries.
> Even under MVCC, update, delete and select .. for update have
> to see the newest tuples.

True.  But my point is that we already have mechanisms to deal with
that set of issues; the trigger code shouldn't concern itself with
the problem.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Hiroshi Inoue
Date:
Subject: Re: Triggered Data Change check
Next
From: Hiroshi Inoue
Date:
Subject: Re: Triggered Data Change check