Re: Triggered Data Change check

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
Cc: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Triggered Data Change check
Date: 2001-11-12 03:11:26
Message-ID: 623.1005534686@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hiroshi Inoue 2001-11-12 03:40:59 Re: Triggered Data Change check
Previous Message Hiroshi Inoue 2001-11-12 03:06:49 Re: Triggered Data Change check

Browse pgsql-patches by date

  From Date Subject
Next Message Hiroshi Inoue 2001-11-12 03:40:59 Re: Triggered Data Change check
Previous Message Hiroshi Inoue 2001-11-12 03:06:49 Re: Triggered Data Change check