| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | daveg <daveg(at)sonic(dot)net> |
| 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-04 21:26:49 |
| Message-ID: | 15607.1312493209@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
daveg <daveg(at)sonic(dot)net> writes:
> On Thu, Aug 04, 2011 at 04:16:08PM -0400, Tom Lane wrote:
>> If this theory is correct then all of the file-related errors ought to
>> match up to recently-vacuumed mapped catalogs or indexes (those are the
>> ones with relfilenode = 0 in pg_class). Do you want to expand your
>> logging of the VACUUM FULL actions and see if you can confirm that idea?
> At your service, what would you like to see?
I was thinking log the before-and-after filenode values each time you do
a VACUUM FULL, and then go through the logs to see if all the
file-related complaints refer to recently obsoleted filenodes.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2011-08-04 21:46:35 | Re: Reduce WAL logging of INSERT SELECT |
| Previous Message | daveg | 2011-08-04 21:09:43 | Re: error: could not find pg_class tuple for index 2662 |