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 02:06:51
Message-ID: 27844.1009505211@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:
> Currently PostgreSQL ignores the update/deleted
> tuples from the first which don't satisfy the
> qualification at the point of snapshot.

It does? It looks to me like we use SnapshotDirty time qual check
and wait for any uncommitted transaction. This essentially means
that we use "latest committed" state, not the query-start snapshot.
Look at _bt_check_unique in nbtinsert.c.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

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