From: | Peter Wiersig <peter(at)friesenpeter(dot)de> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Had a problem with pg_clog |
Date: | 2005-04-27 17:58:59 |
Message-ID: | 20050427175859.GA3232@london087.server4you.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, Apr 24, 2005 at 11:52:11AM -0400, Tom Lane wrote:
> Peter Wiersig <peter(at)friesenpeter(dot)de> writes:
> > On Sat, Apr 23, 2005 at 08:19:31PM -0400, Tom Lane wrote:
> >> Peter Wiersig <peter(at)friesenpeter(dot)de> writes:
> >>> vacuumdb -z miwabar
> >>> PANIC: open of /var/lib/pgsql/data/pg_clog/0000 failed:
> >>> Keine Berechtigung
> >>> server closed the connection unexpectedly
> >>
> >> What PG version is this exactly?
>
> > It's 7.3.9 from SUSE rpms postgresql-7.3.9-3
>
> Hmm. 7.3.9 has all the known patches for hint-bit updates and
> premature clog truncation,
Good.
> Can you repeat this failure from a standing start --- that is,
> initdb, load your data dump, vacuumdb, PANIC?
No, I couldn't.
But I can with the old cluster.
And only if I create the new database with the sequence "psql
template1 <dump_with_create.sql; vacuumdb test".
Other combinations like "createdb test; psql test
<dump_with_create.sql; vacuumdb test" work.
I never tried to restore from a dump created by "pg_dump -C"
before, but this time I was in a hurry to free up more disk space.
--
Peter
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2005-04-27 18:16:16 | Re: populating a table via the COPY command using C code. |
Previous Message | Jon Lapham | 2005-04-27 17:54:09 | restarting after power outage |