Re: Adding ON UPDATE CASCADE to an existing foreign key

From: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
To: Rich Doughty <rich(at)opusvl(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Adding ON UPDATE CASCADE to an existing foreign key
Date: 2006-05-04 16:17:31
Message-ID: 20060504091559.H56325@megazone.bigpanda.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Sebastian Wagner 2006-05-04 17:18:51 Googles sommer of Code 2005 - Postgres Project Proposal - where to discuss? who is responsible? who can mentor?
Previous Message Guy Rouillier 2006-05-04 15:29:56 Re: Segfaults with 8.1.3 on amd64

Browse pgsql-hackers by date

  From Date Subject
Next Message Larry Rosenman 2006-05-04 16:25:00 Re: autovacuum logging, part deux.
Previous Message Rod Taylor 2006-05-04 15:39:50 Re: autovacuum logging, part deux.