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

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Andrew Hammond <andrew(dot)george(dot)hammond(at)gmail(dot)com>
Subject: Re: TOAST versus VACUUM, or "missing chunk number 0 for toast value" identified
Date: 2011-10-28 19:48:22
Message-ID: 1319831239-sup-5174@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-10-28 19:50:56 So where are we on the open commitfest?
Previous Message Alvaro Herrera 2011-10-28 19:47:13 Re: TOAST versus VACUUM, or "missing chunk number 0 for toast value" identified