| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: synchronous commit in dump |
| Date: | 2010-02-23 09:40:23 |
| Message-ID: | 9837222c1002230140p66d0b264xba5a84aff6a6321d@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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. I don't really see how it would help in any other cases -
sync_commit=off helps when you have many small transactions, which
really is the opposite of pg_dump/pg_restore.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2010-02-23 09:56:28 | Re: SR/libpq - outbound interface/ipaddress binding |
| Previous Message | Dimitri Fontaine | 2010-02-23 09:37:10 | Re: tie user processes to postmaster was:(Re: [HACKERS] scheduler in core) |