| From: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: contrib idea |
| Date: | 2001-12-21 08:20:50 |
| Message-ID: | 46C15C39FEB2C44BA555E356FBCD6FA4212883@m0114.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > If you have a foreign key on a column, then whenever the primary key is
> > modified, the following checks may occur:
> >
> > * Check to see if the child row exists (no action)
> > * Delete the child row (cascade delete)
> > * Update the child row (cascade update)
> >
> > All of which will benefit from an index...
>
> OK, then perhaps we should be creating an index automatically? Folks?
The index is only useful where you actually have an on delete or on update
clause. I don't think we want to conditionally create an index. That would
bee too confusing. A contrib, to find "suggested" indexes seems fine.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Kreen | 2001-12-21 08:34:45 | Re: pgcryto failures on freebsd/alpha |
| Previous Message | Bruce Momjian | 2001-12-21 06:51:39 | Re: Status on RC1? |