| From: | decibel <decibel(at)decibel(dot)org> |
|---|---|
| To: | Adrian Klaver <aklaver(at)comcast(dot)net> |
| 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-21 03:57:32 |
| Message-ID: | 2EE63681-B9FD-4934-8028-C2812B705255@decibel.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
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.
--
Decibel!, aka Jim C. Nasby, Database Architect decibel(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828
| From | Date | Subject | |
|---|---|---|---|
| Next Message | c k | 2009-02-21 09:37:50 | How to import/setup library functins |
| Previous Message | Cott Lang | 2009-02-21 00:26:43 | Re: Fixing invalid owners on pg_toast tables in 8.3.5 |