| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Campbell, Lance" <lance(at)illinois(dot)edu> |
| Cc: | "'pgsql-admin(at)postgresql(dot)org'" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: pg_restore new parameter request |
| Date: | 2015-11-23 14:50:13 |
| Message-ID: | 1825.1448290213@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Campbell, Lance" <lance(at)illinois(dot)edu> writes:
> PostgreSQL pg_restore new feature request
> I did some testing last week to see how fast I could get pg_restore to reload data. I found some settings that made a significant speed boost. One request I have is the addition of two parameters to pg_restore.
> --no-indexes
> When this parameter is used during a full restore of a database the indexes would not be applied.
> --only-indexes
> When this parameter is selected during a full restore of a database only the indexes would be applied.
This seems fairly redundant with the existing notion of "dump sections".
Have you experimented with "--section=post-data"?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2015-11-23 14:55:06 | Re: pg_restore new parameter request |
| Previous Message | Campbell, Lance | 2015-11-23 14:37:08 | pg_restore new parameter request |