Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
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

pgsql-bugs by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group