Re: TOAST versus VACUUM, or "missing chunk number 0 for toast value" identified - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: TOAST versus VACUUM, or "missing chunk number 0 for toast value" identified
Date
Msg-id 1319831239-sup-5174@alvh.no-ip.org
Whole thread Raw
In response to Re: TOAST versus VACUUM, or "missing chunk number 0 for toast value" identified  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: TOAST versus VACUUM, or "missing chunk number 0 for toast value" identified
List pgsql-hackers
Excerpts from Alvaro Herrera's message of vie oct 28 16:47:13 -0300 2011:

> BTW we had previous discussions about dropping pg_database's toast
> table.  Maybe this is a good time to do it, even if there's no risk of
> this bug (or the hypothetical circularity detoasting problem) showing up
> there.

Oh, something unrelated I just remembered: we have
pg_database.datlastsysoid which seems unused.  Perhaps we should remove
that column for cleanliness.

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: TOAST versus VACUUM, or "missing chunk number 0 for toast value" identified
Next
From: Tom Lane
Date:
Subject: So where are we on the open commitfest?