From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
---|---|
To: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
Cc: | Rich Doughty <rich(at)opusvl(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [GENERAL] Adding ON UPDATE CASCADE to an existing foreign key |
Date: | 2006-05-04 20:38:25 |
Message-ID: | 20060504203825.GE97354@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Moving to -hackers...
On Thu, May 04, 2006 at 09:17:31AM -0700, Stephan Szabo wrote:
> On Thu, 4 May 2006, Rich Doughty wrote:
>
> > I have a foreign key constraint that I'd like to alter. I'd rather not
> > drop and re-create it due to the size of the table involved. All I need
> > to do is add an ON UPDATE CASCADE.
> >
> > Is it ok to set confupdtype to 'c' in pg_constraint (and will this be
> > all that's needed) or is it safer to drop and recreate the constraint?
>
> I don't think that's going to work, you'd probably need to change the
> function associated with the trigger involved too. It's probably safer to
> do the drop and create.
It would be nice if there was a way to do this that didn't involve
re-validating all the data. Can this be added as a TODO?
--
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-04 20:42:36 | Re: Alternative for vacuuming queue-like tables |
Previous Message | Jim C. Nasby | 2006-05-04 20:33:04 | Re: psql is slow and it does not take much resources |
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2006-05-04 21:01:13 | [bruno@wolff.to: Re: [GENERAL] 8.1.4 anytime soon?] |
Previous Message | Tom Lane | 2006-05-04 19:36:53 | Re: patch review, please: Autovacuum/Vacuum times via stats. |