| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | ogjunk-pgjedan(at)yahoo(dot)com |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Fastest DB restore options |
| Date: | 2007-02-22 16:25:21 |
| Message-ID: | 5872.1172161521@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
ogjunk-pgjedan(at)yahoo(dot)com writes:
> I normally dump with these options:
> -d MyDB --clean --inserts --column-inserts --format=P
> But the last time I tried that, the restore took foreeeeeeeeeeeeeever.
--inserts is pretty expensive.
> So I'm looking for the fastest way to import data from the old DB to the new one. Judging from pg_dump man page the following should be the fastest dump & restore:
> -d MyDB --format=c --ignore-version
Don't use --ignore-version; it's a good way to shoot yourself in the foot.
pg_dump's default behavior is about as good as you can get; there are no
optional switches that will make it faster. What you *can* do is make
sure that the receiving system is properly configured before you start
the restore --- increase maintenance_work_mem and checkpoint_segments
in particular. See this page, especially the last section:
http://www.postgresql.org/docs/8.2/static/populate.html
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jose carlos de la toba duarte | 2007-02-22 16:26:34 | [ADMIN] UNSUBSCRIBE |
| Previous Message | Joshua D. Drake | 2007-02-22 16:05:10 | Re: Fastest DB restore options |