| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Andrew Hammond" <andrew(dot)george(dot)hammond(at)gmail(dot)com> |
| Cc: | Hackers <pgsql-hackers(at)postgresql(dot)org>, "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
| Subject: | Re: the un-vacuumable table |
| Date: | 2008-07-03 21:35:23 |
| Message-ID: | 9538.1215120923@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Andrew Hammond" <andrew(dot)george(dot)hammond(at)gmail(dot)com> writes:
> Does anyone else have any suggestions about what I can do to diagnose this?
The whole thing is pretty mystifying, especially the ENOSPC write
failure on what seems like it couldn't have been a full disk.
> Jun 27 15:54:31 qadb2 postgres[92519]: [44-1] PANIC: could not open
> relation 1663/16386/679439393: No such file or directory
I don't think anyone asked before --- after the restore fails with the
above, does the directory $PGDATA/base/16386/ exist? Although WAL
recovery should attempt to create missing files, I think it won't
try to create missing directories.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-07-03 21:37:44 | Re: CommitFest rules |
| Previous Message | Merlin Moncure | 2008-07-03 20:45:46 | Re: CommitFest rules |