| From: | Glen Barber <glen(dot)j(dot)barber(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Restore time differences between full database dumps and separate schema/data dumps |
| Date: | 2009-12-11 21:14:31 |
| Message-ID: | 4ad871310912111314x3aa52da2yaf8d1743c73911cc@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi Tom,
On Thu, Dec 10, 2009 at 6:42 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Glen Barber <glen(dot)j(dot)barber(at)gmail(dot)com> writes:
>> When schema/data are separated, is the restore treated as INSERTs?
>
> No, but you'll still get killed on performance by other factors,
> particularly incremental index building and retail foreign key checks.
> I recommend a close read of
> http://www.postgresql.org/docs/8.4/static/populate.html
>
> What you'll want to do is separate the load into three phases
> corresponding to the order that a combined schema+data dump
> does it.
>
Thanks for the pointer.
Regards,
--
Glen Barber
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2009-12-12 02:17:49 | Re: Postgres.exe Process taking too much memory and CPU usage - making the system extremely slow. |
| Previous Message | John R Pierce | 2009-12-11 18:49:47 | Re: Postgres.exe Process taking too much memory and CPU usage - making the system extremely slow. |