Re: error: could not find pg_class tuple for index 2662

From: daveg <daveg(at)sonic(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: error: could not find pg_class tuple for index 2662
Date: 2011-08-06 00:01:47
Message-ID: 20110806000147.GL14353@sonic.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Aug 05, 2011 at 12:10:31PM -0400, Tom Lane wrote:
> I wrote:
> > Ahh ... you know what, never mind about stack traces, let's just see if
> > the attached patch doesn't fix it.
>
> On reflection, that patch would only fix the issue for pg_class, and
> that's not the only catalog that gets consulted during relcache reloads.
> I think we'd better do it as attached, instead.
>
> regards, tom lane

Should this be applied in addition to the earlier patch, or to replace it?

-dg

--
David Gould daveg(at)sonic(dot)net 510 536 1443 510 282 0869
If simplicity worked, the world would be overrun with insects.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-08-06 00:48:25 Re: error: could not find pg_class tuple for index 2662
Previous Message Peter Eisentraut 2011-08-06 00:01:25 Re: cataloguing NOT NULL constraints