Re: PG dump and restore - Mailing list pgsql-general

From Dennis C
Subject Re: PG dump and restore
Date
Msg-id AANLkTinIuYy78k5smbMXJBOqes4dqjhSU5_5YcWsZAne@mail.gmail.com
Whole thread Raw
In response to Re: PG dump and restore  (Adrian Klaver <adrian.klaver@gmail.com>)
Responses Re: PG dump and restore  (Adrian Klaver <adrian.klaver@gmail.com>)
Re: PG dump and restore  (Thom Brown <thombrown@gmail.com>)
Re: PG dump and restore  (Thom Brown <thombrown@gmail.com>)
List pgsql-general
OK well the gunzip seemed to "do the trick," but I don't recall before having to do anything other than run the pg_restore command.  Anyway, thanks to everyone for all your help!


On Fri, Jun 25, 2010 at 11:29 AM, Adrian Klaver <adrian.klaver@gmail.com> wrote:
On 06/25/2010 09:04 AM, Dennis C wrote:
It says "Trading-Access: gzip compressed data, from Unix"

About the idea of not using pg_restore for these dumps, what I'm still
missing is how it's worked for all these years before.  Are there now more
stringent standards being enforced?



You have restored from these dumps using pg_restore?

The command below says create a plain text file that has commands to clean database objects before recreating and store text in file ./Trading-Access using gzip compression at level 5:


/opt/local/lib/postgresql84/bin/pg_dump -c -f ./Trading-Access -Z 5 Trading-Access

To restore I would think you need to gunzip ./Trading-Access and then feed the file to psql.


--
Adrian Klaver
adrian.klaver@gmail.com

pgsql-general by date:

Previous
From: John R Pierce
Date:
Subject: Re: pl-perl for 64 bits in Solaris 9
Next
From: Adrian Klaver
Date:
Subject: Re: PG dump and restore