| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
| Cc: | Peter Childs <blue(dot)dragon(at)blueyonder(dot)co(dot)uk>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Alter Contraint |
| Date: | 2003-02-07 15:32:58 |
| Message-ID: | 27612.1044631978@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> writes:
> AFAIK, SET CONSTRAINTS only lets you change the check time of
> deferrable constraints, it doesn't let you make a not deferrable
> constraint deferrable.
Good point, if your constraint wasn't deferrable to begin with then
you can't make it so with SET. But on the other hand, making it so
is a one-time operation, so deleting and recreating the constraint
doesn't seem that big a deal. If I recall Peter's original message,
he was mainly concerned about flipping from the not-deferred to deferred
state and back efficiently --- that's what SET seems designed for.
I have nothing against providing an ALTER if someone wants to do the
legwork, but it doesn't seem like a high-priority problem ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-02-07 15:35:42 | Re: converting Oracle to postgres |
| Previous Message | Lincoln Yeoh | 2003-02-07 15:27:29 | Re: converting Oracle to postgres |