From: | Dennis C <dcswest(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
Cc: | questions(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
Subject: | Re: PG dump and restore |
Date: | 2010-06-25 23:59:17 |
Message-ID: | AANLkTinIuYy78k5smbMXJBOqes4dqjhSU5_5YcWsZAne@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(dot)klaver(at)gmail(dot)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(dot)klaver(at)gmail(dot)com
>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2010-06-26 00:18:54 | Re: PG dump and restore |
Previous Message | John R Pierce | 2010-06-25 23:00:15 | Re: pl-perl for 64 bits in Solaris 9 |