On Sun, Apr 24, 2005 at 11:52:11AM -0400, Tom Lane wrote:
> Peter Wiersig <[EMAIL PROTECTED]> writes:
> > On Sat, Apr 23, 2005 at 08:19:31PM -0400, Tom Lane wrote:
> >> Peter Wiersig <[EMAIL PROTECTED]> writes:
> >>> vacuumdb -z miwabar
> >>> PANIC: open of /var/lib/pgsql/data/pg_clog/ failed:
Peter Wiersig <[EMAIL PROTECTED]> writes:
> On Sat, Apr 23, 2005 at 08:19:31PM -0400, Tom Lane wrote:
>> Peter Wiersig <[EMAIL PROTECTED]> writes:
>>> vacuumdb -z miwabar
>>> PANIC: open of /var/lib/pgsql/data/pg_clog/ failed:
>>> Keine Berechtigung
>>> server closed the connection unexpectedl
On Sat, Apr 23, 2005 at 08:19:31PM -0400, Tom Lane wrote:
> Peter Wiersig <[EMAIL PROTECTED]> writes:
> > vacuumdb -z miwabar
> > PANIC: open of /var/lib/pgsql/data/pg_clog/ failed:
> >Keine Berechtigung
> > server closed the connection unexpectedly
>
> What PG version
Peter Wiersig <[EMAIL PROTECTED]> writes:
> vacuumdb -z miwabar
> PANIC: open of /var/lib/pgsql/data/pg_clog/ failed:
>Keine Berechtigung
> server closed the connection unexpectedly
What PG version is this exactly? We have had some bugs of that
ilk in the past,
Hi List,
I had a database with a 8 Mb pg_dump file with 1.7 Gb in PG_DATA.
I dropped the database and tried to recreate the db with this
step:
psql template1 < data.sql
All tables and all data was restored and to help accessing the db
I tried to vacuum analyze it, yielding this error message:
