Re: order of row processing affects updates

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Paramveer(dot)Singh(at)trilogy(dot)com
Cc: Greg Stark <gsstark(at)mit(dot)edu>, pgsql-general(at)postgresql(dot)org
Subject: Re: order of row processing affects updates
Date: 2004-09-20 14:25:18
Message-ID: 11202.1095690318@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Paramveer(dot)Singh(at)trilogy(dot)com writes:
> Can someone tell me why postgres does not support deferring unique
> constraints?

Because no one's implemented it. The existing unique-check code is
associated with insertion of a new index entry, and it's nontrivial
to refactor it into a deferrable operation. There is a TODO item
for this, but don't hold your breath ...

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Matthew Wilson 2004-09-20 14:27:41 How to get most frequent and least frequent values in a column?
Previous Message lists 2004-09-20 13:55:17 Weird behavior with selects and composite data types