From: | Alumne FIB - GUSTAVO PEREZ QUEROL <e7640227(at)est(dot)fib(dot)upc(dot)es> |
---|---|
To: | |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: dump among different versions of postgreSQL |
Date: | 2003-09-18 15:34:04 |
Message-ID: | 3F69D06C.272F3B7@est.fib.upc.es |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Setting the verbose mode (which usually uses to be very usefull ;) ), showed me something like this while restoring :
BEGIN, still in transaction (more or less)
which made me think that the autocommit was disabled. This feature in series 7.3.x is very usefull to me but, as I checked,
in the restore file there are two BEGIN's. That avoided pg_restore to resolve the OID's succesfully.
Right now, turning the autocommit to true, while restore (and disabling it later), allows me to restore any database.
Thanks for your interest,
Gustavo
"Kuhn, Dylan K (4520500D)" wrote:
> I've successfully dumped and restored a database containing large objects with 7.3.3 and previous versions. I've used the 'tar' archive format something like this:
>
> % pg_dump -F t -b dbwithlos | gzip > dump.tar.gz
> % zcat dump.tar.gz | pg_restore -d restoredbwithlos
>
> Dylan Kuhn
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-09-18 16:16:10 | Re: [PERFORM] How to force an Index ? |
Previous Message | Kuhn, Dylan K (4520500D) | 2003-09-18 15:16:20 | Re: dump among different versions of postgreSQL |