From: | Emi Lu <emilu(at)encs(dot)concordia(dot)ca> |
---|---|
To: | raghu ram <raghuchennuru(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Temporally disabled foreign key constraint check? |
Date: | 2011-10-21 15:49:31 |
Message-ID: | 4EA1948B.1020802@encs.concordia.ca |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thank you first.
I believe that upate pg_class can only be done by superuser, right?
Besides, if I need the whole schema's foreign keys to be disabled and
then enabled later.
Is there a simple command could do it? Similar to mysql's "set
FOREIGN_KEY_CHECKS = false/true"?
Emi
On 10/21/2011 11:12 AM, raghu ram wrote:
>
>
> On Fri, Oct 21, 2011 at 8:33 PM, Emi Lu <emilu(at)encs(dot)concordia(dot)ca
> <mailto:emilu(at)encs(dot)concordia(dot)ca>> wrote:
>
> Good morning,
>
>
> Is there a way to temporally disabled foreign key constraints
> something like:
>
> SET FOREIGN_KEY_CHECKS=0
>
> When population is done, will set FOREIGN_KEY_CHECKS=1
>
>
> You can disable *triggers* on a table (which will disable all the FK
> constraints, but not things like 'not nul' or 'unique').
>
> For Disable:
>
> update pg_class set reltriggers=0 where relname = 'TEST';
>
> For Enable:
>
> update pg_class set reltriggers = count(*) from pg_trigger where
> pg_class.oid=tgrelid and relname='TEST';
>
> --Raghu
--
Emi Lu, ENCS, Concordia University, Montreal H3G 1M8
emilu(at)encs(dot)concordia(dot)ca +1 514 848-2424 x5884
From | Date | Subject | |
---|---|---|---|
Next Message | Henry Drexler | 2011-10-21 17:02:49 | Re: plpgsql at what point does the knowledge of the query come in? |
Previous Message | Andreas Kretschmer | 2011-10-21 15:22:31 | Re: Temporally disabled foreign key constraint check? |