Re: problems with table corruption continued

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Brian Hirt" <bhirt(at)mobygames(dot)com>
Cc: "Postgres Hackers" <pgsql-hackers(at)postgresql(dot)org>, "Brian A Hirt" <bhirt(at)berkhirt(dot)com>
Subject: Re: problems with table corruption continued
Date: 2001-12-18 18:53:37
Message-ID: 17494.1008701617@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Brian Hirt" <bhirt(at)mobygames(dot)com> writes:
> Great, I'm also trying to create a reproducable test case for the original
> problem i reported with duplicate rows/oids/pkeys. Maybe both problems are
> a result of the same bug; i don't know.

Were the duplicate rows all in tables that had functional indexes based
on functions similar to developer_aka_search_name? The problem we're
seeing here seems to be due to VACUUM not being able to cope with the
side effects of the SELECT inside the index function.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mikheev, Vadim 2001-12-18 18:55:41 Re: Deadlock condition in current sources
Previous Message Jason Earl 2001-12-18 18:53:04 Re: Concerns about this release