| From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Open items |
| Date: | 2003-10-28 04:04:04 |
| Message-ID: | 20031027200312.Q47314@megazone.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 27 Oct 2003, Bruce Momjian wrote:
> Marc G. Fournier wrote:
> >
> >
> > On Mon, 27 Oct 2003, Bruce Momjian wrote:
> >
> > > Changes
> > > -------
> > > Allow superuser (dba?) the ability to turn off foreign key checks/all
> > > constraints/triggers, not settable from postgresql.conf?
> >
> > feature, not bug fix, no?
>
> It became important when everyone realized that 7.4 would be first major
> upgrade with full foreign key checking --- prior to that we did CREATE
> CONSTRAINT TRIGGER that didn't check data. Basically, that's how it got
> on the open item list.
Have we heard anything about whether this is still as important given
the other optimizations to the alter table case from people with large
enough data sets to notice?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-10-28 04:16:34 | Re: Horology failures |
| Previous Message | Christopher Kings-Lynne | 2003-10-28 03:53:47 | Re: Horology failures |