Re: VACUUM FULL versus system catalog cache invalidation

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Robert Haas" <robertmhaas(at)gmail(dot)com>, "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 19:22:47
Message-ID: 4E453737020000250003FE81@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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".

Based on this, I don't think we want to wait for bug reports. One
would be too many.

+1 for backpatching a fix.

> As for it not being the last bug, no, it's probably not. That's a
> pretty sucky excuse for not fixing it too.

I agree.

-Kevin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2011-08-12 19:25:43 Re: VACUUM FULL versus system catalog cache invalidation
Previous Message Heikki Linnakangas 2011-08-12 19:16:50 Inserting heap tuples in bulk in COPY