Re: creating CHECK constraints as NOT VALID - Mailing list pgsql-hackers

From Jaime Casanova
Subject Re: creating CHECK constraints as NOT VALID
Date
Msg-id BANLkTik0qQ+t3zgX-gHZUm-4EMN2FTMwpg@mail.gmail.com
Whole thread Raw
In response to Re: creating CHECK constraints as NOT VALID  (Jaime Casanova <jaime@2ndquadrant.com>)
List pgsql-hackers
On Tue, Jun 14, 2011 at 4:41 PM, Jaime Casanova <jaime@2ndquadrant.com> wrote:
> On Tue, Jun 14, 2011 at 4:14 PM, Alvaro Herrera
> <alvherre@commandprompt.com> wrote:
>> Excerpts from Alvaro Herrera's message of lun jun 13 18:08:12 -0400 2011:
>>> Excerpts from Dean Rasheed's message of sáb jun 11 09:32:15 -0400 2011:
>>
>>> > I think that you also need to update the constraint exclusion code
>>> > (get_relation_constraints() or nearby), otherwise the planner might
>>> > exclude a relation on the basis of a CHECK constraint that is not
>>> > currently VALID.
>>>
>>> Ouch, yeah, thanks for pointing that out.  Fortunately the patch to fix
>>> this is quite simple.  I don't have it handy right now but I'll post it
>>> soon.
>>
>> Here's the complete patch.
>>
>
> this doesn't apply
>

oops! sorry for the noise... this was gmail problem...
the patch was expanded as text, instead of an attachments and when i
copy/paste it it should have moved something... copy'ing from archives
instead was good

--
Jaime Casanova         www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación


pgsql-hackers by date:

Previous
From: Mark Kirkwood
Date:
Subject: Re: Re: patch review : Add ability to constrain backend temporary file space
Next
From: Robert Creager
Date:
Subject: Re: Why polecat and colugos are failing to build back branches