| From: | Wes <wespvp(at)syntegra(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Adding foreign key constraints without integrity |
| Date: | 2006-06-19 04:08:36 |
| Message-ID: | C0BB8D74.2876A%wespvp@syntegra.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 6/18/06 10:48 PM, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> My database reload is currently taking about 6 hours to load the data, 42
>> hours to reindex, and about another 40 hours or so to check the foreign key
>> constraints (about 1.2 billion rows).
>
> What PG version is this, and what have you got maintenance_work_mem set to?
> Undersized m_w_m would hurt both index build and FK checking ...
Sorry, forgot that info..
PG is 8.1.4 (I'm testing an upgrade from 7.3.4 to 8.1.4).
maintenance_work_mem is set to 983025 - 1.5 times the previous value of
655350. Current RSS of postmaster is about 1.3 GB.
System memory is 2GB (would like more, but...). Data is on one array
(hardware RAID 5 of eight 73 GB 10k SCSI drives), indexes on another
(hardware RAID 5 of five 15K 146 GB SCSI drives on a separate channel), and
pg_xlog on a third RAID 1 on a third channel). There are two 2.4 GHz Xeon
processors).
Wes
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2006-06-19 07:24:04 | Re: Question about openSSL |
| Previous Message | Tom Lane | 2006-06-19 03:48:35 | Re: Adding foreign key constraints without integrity check? |