To: "Simon Kinsella" <simon@bluefiresystems.co.uk>
cc: pgsql-sql@postgresql.org
Subject: Re: Possible to emulate pre-8.2 behaviour of SET CONSTRAINTS? 
In-reply-to: <20070121235235.BADE3197346@smtp06l.fasthosts.co.uk> 
References: <20070121235235.BADE3197346@smtp06l.fasthosts.co.uk>
Comments: In-reply-to "Simon Kinsella" <simon@bluefiresystems.co.uk>
	message dated "Sun, 21 Jan 2007 23:52:28 +0000"
Date: Sun, 21 Jan 2007 22:36:48 -0500
Message-ID: <1893.1169437008@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

"Simon Kinsella" <simon@bluefiresystems.co.uk> writes:
> My system currently runs on PostgreSQL 8.1 and makes use of the old
> behaviour of SET CONSTRAINTS, namely that the command is applied to all
> constraints that match the specified name.

Unfortunately that was pretty far away from what the SQL spec says :-(

> This makes it very easy to write
> a general-case function that can change the DEFERRED mode on a given
> constraint that is present in several similar schemas (sounds odd maybe but
> it works very well in my case!). 

I think you could do it fairly easily still, eg

	for rec in select nspname from pg_namespace n join pg_constraint c on n.oid = c.connamespace where conname = $1 loop
           execute 'set constraints ' || quote_ident(rec.nspname) || '.' || quote_ident($1) || ' immediate';
        end loop;

Exceedingly untested, but something close to this seems like it'd solve
your problem.

			regards, tom lane