From: | Adrian Klaver <aklaver(at)comcast(dot)net> |
---|---|
To: | decibel <decibel(at)decibel(dot)org> |
Cc: | sharmi jo <sharmi_jo(at)yahoo(dot)com>, General postgres mailing list <pgsql-general(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Subject: | Re: NOVALIDATE in postgresql? |
Date: | 2009-02-22 19:14:32 |
Message-ID: | 200902221114.32821.aklaver@comcast.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Friday 20 February 2009 7:57:32 pm decibel wrote:
> On Feb 19, 2009, at 1:49 PM, Adrian Klaver wrote:
> > From the Oracle manual:
> > ENABLE NOVALIDATE means the constraint is checked for new or
> > modified rows, but existing data may violate the constraint.
> >
> > So you are looking for an incomplete constraint?
>
> More likely they want to add a constraint but can't afford the time
> it would take to scan the table while holding an exclusive lock. At
> least that's the situation we're facing at work.
I get it now, basically validate on demand, so the cost is spread out instead of
incurred at the ALTER TABLE command.
>
> FWIW, I've been talking to Command Prompt about developing a fix for
> this, targeting inclusion in 8.5. I think Alvaro and I have come up
> with a reasonably plan, but there hasn't been time to present it to
> the community yet.
--
Adrian Klaver
aklaver(at)comcast(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Angelo Astorga | 2009-02-22 19:46:37 | Cambiando Postgresql 7.4.3 a 8.1.11 !!! |
Previous Message | Gerd Koenig | 2009-02-22 18:58:47 | Re: PostgreSQL CE? |