From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: synchronous commit in dump |
Date: | 2010-02-24 16:55:34 |
Message-ID: | 603c8f071002240855q1e6492a0oe2490a4c2a13337b@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Feb 23, 2010 at 6:54 PM, Jaime Casanova
<jcasanov(at)systemguards(dot)com(dot)ec> wrote:
> On Tue, Feb 23, 2010 at 4:40 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> 2010/2/23 Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>:
>>> Hi,
>>>
>>> it's safe to set synchrounous_commit to off in a pg_dump generated
>>> script? if yes, would this help to the performance of restore a
>>> database?
>>
>> It might help if you're dumping as individual inserts and not COPY,
>> but if you're doing that you're not asking for performance in the
>> first place.
>
> That isn't necesarily true. Maybe you don't have shell access to the
> database server
> but just trough pgadmin or something like that...
>
> in that env the copy of the dumps won't work so you need to make the backup with
> inserts (by need) and still want some performance
I don't see why that would preclude using COPY. But anyway in that
case you could still run the restore with -1.
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2010-02-24 16:59:30 | Re: Small change of the HS document |
Previous Message | Heikki Linnakangas | 2010-02-24 16:48:00 | Re: A thought on Index Organized Tables |