Skip site navigation (1) Skip section navigation (2)

Re: special integrity constraints

From: Erik Thiele <erik(at)thiele-hydraulik(dot)de>
To: Bruno Wolff III <bruno(at)wolff(dot)to>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: special integrity constraints
Date: 2004-03-22 16:21:21
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-docspgsql-sql
On Mon, 22 Mar 2004 09:12:11 -0600
Bruno Wolff III <bruno(at)wolff(dot)to> wrote:

> On Mon, Mar 22, 2004 at 14:10:42 +0100,
>   Erik Thiele <erik(at)thiele-hydraulik(dot)de> wrote:
> > 
> > it means (((count_rows(a)+count_rows(b)) modulo 2) == 0)
> OK, that means my FK suggestion won't help. The other suggestion about
> putting triggers on "a" and "b" to update a count in another table
> that has a deferred check constraint on it may be your best bet.
> This will be a source of contention, but that may or may not be all
> that important depending on how often you are updating "a" and "b".

there is no such thing as a deferred check constraint:


This controls whether the constraint can be deferred. A constraint that
is not deferrable will be checked immediately after every command.
Checking of constraints that are deferrable may be postponed until the
end of the transaction (using the SET CONSTRAINTS command). NOT
DEFERRABLE is the default. 

!!! Only foreign key constraints currently accept
this clause. All other constraint types are not deferrable. !!!


Erik Thiele

In response to


pgsql-docs by date

Next:From: Tom LaneDate: 2004-03-22 16:21:23
Previous:From: Bruno Wolff IIIDate: 2004-03-22 15:12:11
Subject: Re: special integrity constraints

pgsql-sql by date

Next:From: Erik ThieleDate: 2004-03-22 16:25:44
Subject: Re: special integrity constraints
Previous:From: Dana HudesDate: 2004-03-22 15:56:36
Subject: Re: inverse of "day of year"

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group