Re: Corrupt database? 8.1/FreeBSD6.0

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Jeff Amiel <becauseimjeff(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Corrupt database? 8.1/FreeBSD6.0
Date: 2007-01-18 16:52:23
Message-ID: 28018.1169139143@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Tom Lane wrote:
>> But it seems that we need a band-aid for 8.1 and earlier. The simplest
>> fix I can think of is for vacuum not to attempt to advance the
>> datvacuumxid/datfrozenxid fields if it skipped over any temp tables of
>> other backends. That's a bit nasty, since in a database making heavy
>> use of temp tables, you might do a whole lot of vacuums without ever
>> meeting that condition. Anyone have a better idea?

> That seems nasty. Can we examine the xmin of the pg_class entry for
> temp tables instead?

No, because any sort of schema update on the temp table would rewrite
its pg_class row with a newer version. You couldn't assume that the
pg_class row is older than what's in the table. Consider this perfectly
reasonable scenario:

CREATE TEMP TABLE foo ...
COPY foo FROM ...
CREATE INDEX ... <- must set relhasindex

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Patrick Earl 2007-01-18 17:31:26 Re: GUID/UUID Support
Previous Message Jorge Godoy 2007-01-18 16:50:04 Re: [1/2 OFF] Varlena.com inaccessible from .br (Blocked?)

Browse pgsql-hackers by date

  From Date Subject
Next Message Teodor Sigaev 2007-01-18 17:24:39 Re: Design notes for EquivalenceClasses
Previous Message Alvaro Herrera 2007-01-18 16:42:49 Re: Corrupt database? 8.1/FreeBSD6.0