X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id C5537DAECE for ; Tue, 25 Oct 2005 22:38:18 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 23336-04 for ; Wed, 26 Oct 2005 01:38:14 +0000 (GMT) Received: from candle.pha.pa.us (candle.pha.pa.us [64.139.89.126]) by svr1.postgresql.org (Postfix) with ESMTP id 40559DAEA6 for ; Tue, 25 Oct 2005 22:38:16 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id j9Q1cFL17707; Tue, 25 Oct 2005 21:38:15 -0400 (EDT) From: Bruce Momjian Message-Id: <200510260138.j9Q1cFL17707@candle.pha.pa.us> Subject: Re: ?Equiv to oracle (ENABLE|DISABLE) (CONSTRAINT|TRIGGER) statements? In-Reply-To: <200510261113.43685.dave.bath@unix.net> To: dave.bath@unix.net Date: Tue, 25 Oct 2005 21:38:15 -0400 (EDT) Cc: pgsql-sql@postgresql.org X-Mailer: ELM [version 2.4ME+ PL121 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.013 required=5 tests=[AWL=0.013] X-Spam-Level: X-Archive-Number: 200510/298 X-Sequence-Number: 23151 Please see the 8.1 beta release notes for new capabilities in that release. --------------------------------------------------------------------------- Bath, David wrote: > Folks, > > Summary: > Does postgresql have equivalents to the following Oracle statements? > DISABLE CONSTRAINT ... > ENABLE CONSTRAINT ... > DISABLE TRIGGER ... > ENABLE TRIGGER ... > > Background: > One of the advantages of Oracle over some competitors such as MS-SQL > and Sybase is the ability to toggle a constraint or trigger on and > off, without blatting it, and without the hassle of finding any > code and any accessory information (like comments, permissions...). > > BTW, I personally put C-style comments at the front of the clause so > I can get the why's/how's into the syscatalogs - but I wear jackboots > where documentation is concerned :-) and get at these for autodoccing > and/or generation of meaningful messages to users when raising > exception messages from the server. > > This capability is especially useful when there is some disgusting > data-munging by a DBA, not just for import/export. > > I've tried grovelling through the sql from a pg_dump invoked with > --disable-triggers, but it has no enable/disable triggers or > constraints, merely creating primary/foreign constraints AFTER > issuing the COPY. > > Yep, I'd expect this ONLY to work when issued by someone with DBA > privs (and maybe the target object owner, although I imagine reasons > that /might/ be a bad idea for paranoid info management governance). > > Thanks in advance > -- > David T. Bath > dave.bath@unix.net > > > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend > -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073