| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Enzo Daddario <enzo(at)pienetworks(dot)com>, PGADMIN <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Constraint question |
| Date: | 2006-05-15 15:12:49 |
| Message-ID: | 20060515151249.GE26212@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Sun, May 14, 2006 at 10:50:50PM -0400, Tom Lane wrote:
> Enzo Daddario <enzo(at)pienetworks(dot)com> writes:
> > I am now required the remove thousands of obsolete records from table
> > "X" and even though I have removed all related rows in all related
> > tables, the deletion of rows in table "X" is taking WAY TOO LONG.
>
> You need to put indexes on the referencing columns. Then start a fresh
> session for doing the actual deletes (FK check plans are usually cached
> per-session).
Would SET CONSTRAINTS ... DEFERRED not help, or does it still use the
same machinery to do the checking, regardless of how much data there is
to check?
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-05-15 15:16:36 | Re: increasing max_fsm_pages. |
| Previous Message | Xu, Xiaoyi (Rocky) FSM | 2006-05-15 15:09:25 | Error in Access |