Re: Serializable access giving wrong error messages?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
Cc: Mikko Vierula <mikko(dot)vierula(at)elektroniikkatyo(dot)fi>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Serializable access giving wrong error messages?
Date: 2001-12-28 03:04:38
Message-ID: 28259.1009508678@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> writes:
> What I meant is e.g.
> update t set .. = .. where ...;
> PostgreSQL ignores the tuples which don't satisfy the
> where clause at the point when the query started(or
> when the transaction started in serializable mode)
> even though it happend to look already update/delete
> (/insert)ed tuples.

Sure, but what we were discussing was the "duplicate key" error issued
by nbtinsert.c. AFAICS that depends on latest-commit status, not on
snapshots. Perhaps that behavior is itself a bug? If so, how would
you change it?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Hiroshi Inoue 2001-12-28 04:13:50 Re: Serializable access giving wrong error messages?
Previous Message Hiroshi Inoue 2001-12-28 02:24:25 Re: Serializable access giving wrong error messages?