| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | renzo(at)tzi(dot)de |
| Cc: | "Michael Fuhr" <mike(at)fuhr(dot)org>, s(dot)gnanavel(at)gmail(dot)com, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Strange delete behaviour |
| Date: | 2005-08-01 14:13:42 |
| Message-ID: | 2564.1122905622@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Renzo Kottmann" <renzo(at)tzi(dot)de> writes:
> "t_annotation_ann_startnode_id_fkey" FOREIGN KEY (ann_startnode_id)
> REFERENCES t_node(node_global_id) MATCH FULL
> "t_annotation_ann_endnode_id_fkey" FOREIGN KEY (ann_endnode_id)
> REFERENCES t_node(node_global_id) MATCH FULL
You need indexes on ann_startnode_id and ann_endnode_id. There might be
some other missing indexes too --- check each of your foreign key
constraints.
Postgres doesn't force you to keep an index on the referencing side of a
foreign key ... but if you want deletes from the master table to be
fast, you'd better have one.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Fein | 2005-08-01 14:19:39 | Schema Pivileges was Re: Alter privileges for all tables |
| Previous Message | Michael Fuhr | 2005-08-01 14:11:03 | Re: Strange delete behaviour |