Re: Short-circuiting FK check for a newly-added field

From: David Fetter <david(at)fetter(dot)org>
To: Decibel! <decibel(at)decibel(dot)org>
Cc: Postgres List <pgsql-general(at)postgresql(dot)org>
Subject: Re: Short-circuiting FK check for a newly-added field
Date: 2008-05-21 12:00:51
Message-ID: 20080521120051.GA13726@fetter.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, May 20, 2008 at 02:25:15PM -0400, Decibel! wrote:
> I need to add a field to a fairly large table. In the same alter statement
> I'd like to add a FK constraint on that new field. Is there any way to
> avoid the check of the table that the database is doing right now? The
> check is pointless because the newly added field is nothing but NULLs.
>
> This is version 8.1.mumble.

Have you tried making the FK constraint INITIALLY DEFERRED?

Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Sim Zacks 2008-05-21 12:23:32 bytea case sensitivity
Previous Message Ivan Sergio Borgonovo 2008-05-21 11:48:51 Re: Postgresql MVCC, Read Committed Isolation Level and taking "snapshot"