thanks for answering so quickly!
The error occurs for me using pg_dump and pg_restore on postgres 8.0.3
running on RedHat ES4. But also occurs if I take the dump from the Linux
box and run restore on a winxp box with postgres 8.0.2.
I would definetely be willing to create a self contained test case but I
am not sure what that would be. I can create a dump file from a test
database, but that would be after using pg_dump so you could not check
that. Do you want me to create a database, shut it down and zip up the
database files? Which files would those be?
Is there a way for me to find out if the dump file created with -Fc does
contain information on the indexes?
>> I have tried to backup my postgres database with
>> pg_dump -Fc $db > ~/backups/$db.backup.c
>> and restore it with:
>> createdb -U postgres -D aestel_admin -T template0 restoreTMP
>> pg_restore -d restoreTMP -U postgres $db.backup.c
>> I do not get any error messages but none of my indexes are created.
>Works for me ... can you create a self-contained test case? What PG
>version are you using, anyway (and are you sure the pg_dump and
>pg_restore programs are of the same version)?
> regards, tom lane
In response to
pgsql-admin by date
|Next:||From: Jeff Frost||Date: 2005-06-25 21:25:15|
|Subject: Re: restoring wal archive and pg_xlog dir|
|Previous:||From: Tom Lane||Date: 2005-06-25 19:49:42|
|Subject: Re: listening on tcp socket instead of unix domain |