| From: | "Jaime Casanova" <jcasanov(at)systemguards(dot)com(dot)ec> |
|---|---|
| To: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: parallel restore |
| Date: | 2009-01-07 03:56:50 |
| Message-ID: | 3073cc9b0901061956n168ef99csafa37065f1661025@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 6, 2009 at 5:54 PM, Andrew Dunstan <andrew(at)dunslane(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2009-01-07 04:25:54 | Re: log output of vxid |
| Previous Message | Bruce Momjian | 2009-01-07 03:39:11 | Re: HAVE_FSEEKO for WIN32 |