From: | tgl(at)svr1(dot)postgresql(dot)org (Tom Lane) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql-server/src/backend/utils/time tqual.c |
Date: | 2003-09-22 00:47:23 |
Message-ID: | 20030922004723.AE82BD1B4F0@svr1.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
CVSROOT: /cvsroot
Module name: pgsql-server
Changes by: tgl(at)svr1(dot)postgresql(dot)org 03/09/21 21:47:23
Modified files:
src/backend/utils/time: tqual.c
Log message:
HeapTupleSatisfiesVacuum() needs to be more careful about the
difference between INSERT_IN_PROGRESS and DELETE_IN_PROGRESS for
tuples inserted and then deleted by a concurrent transaction.
Example of bug:
regression=# create table foo (f1 int);
CREATE TABLE
regression=# begin;
BEGIN
regression=# insert into foo values(1);
INSERT 195531 1
regression=# delete from foo;
DELETE 1
regression=# insert into foo values(1);
INSERT 195532 1
regression=# create unique index fooi on foo(f1);
ERROR: could not create unique index
DETAIL: Table contains duplicated values.
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2003-09-22 00:53:38 | Re: Improving REINDEX for system indexes (long) |
Previous Message | Peter Eisentraut - PostgreSQL | 2003-09-22 00:27:02 | pgsql-server/src bin/pg_dump/po/de.po bin/psql ... |