Re: parallel restore - Mailing list pgsql-hackers

From Jaime Casanova
Subject Re: parallel restore
Date
Msg-id 3073cc9b0901061956n168ef99csafa37065f1661025@mail.gmail.com
Whole thread Raw
In response to Re: parallel restore  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: parallel restore  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Tue, Jan 6, 2009 at 5:54 PM, Andrew Dunstan <andrew@dunslane.net> wrote:
>
> Well, the only reason it was needed was because you can't run a parallel
> restore in a single transaction. If the whole restore is run in a single
> transaction then truncate before load should be unnecessary.
>

doesn't understand you. Anyway i tried to run with
--truncate-before-load and got a message about that should be
necessary to run TRUNCATE CASCADE instead.

Sorry, don't have the real message at hand. Seems like the recently
applied patch about fseeko made this one to no longer apply cleanly

--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: HAVE_FSEEKO for WIN32
Next
From: Bruce Momjian
Date:
Subject: Re: log output of vxid