Re: TOAST versus VACUUM, or "missing chunk number 0 for toast value" identified

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Andrew Hammond" <andrew(dot)george(dot)hammond(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: TOAST versus VACUUM, or "missing chunk number 0 for toast value" identified
Date: 2011-10-28 19:58:11
Message-ID: 28851.1319831891@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> If we made the commit sequence number more generally available,
> incrementing it at the point of visibility change under cover of
> ProcArrayLock, and including the then-current value in a Snapshot
> object when built, would that help with this at all?

No, because we need a back-patchable fix. Even going forward,
I don't find the idea of flushing syscache entries at transaction
end to be especially appealing.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-10-28 20:01:22 Re: So where are we on the open commitfest?
Previous Message Kevin Grittner 2011-10-28 19:54:26 Re: TOAST versus VACUUM, or "missing chunk number 0 for toast value" identified