Re: VACUUM FULL versus system catalog cache invalidation

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: VACUUM FULL versus system catalog cache invalidation
Date: 2011-08-12 20:03:56
Message-ID: CA+Tgmob+0vMG+muUr8_4PCHo+VbkcKMCiGETu=Xw-n_3SQPBqg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Aug 12, 2011 at 3:14 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> In any case, it is now clear to me that this bug is capable of eating
> peoples' databases, as in "what just happened to our most critical
> table?  Uh, it's not there anymore, boss, but we seem to have duplicate
> pg_class entries for this other table".

OK, I take your point. That's certainly scary enough to worry about.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-08-12 20:06:37 Re: index-only scans
Previous Message Heikki Linnakangas 2011-08-12 20:03:08 Re: index-only scans