Re: [GENERAL] Re: [GENERAL] Forcefully adding a CHECK constrained

2012-05-28 Thread Tom Lane
"=?utf-8?B?Q2F0YWxpbih1eCkgTS4gQm9pZQ==?=" writes: > I hope I make myself clear now: I want a possibility to add a CHECK that will > be used for partitioning without having to read all data for validation. Basically, this is unlikely to be accepted, because it does not conform with the project's

[GENERAL] Re: [GENERAL] Forcefully adding a CHECK constrained

2012-05-27 Thread Catalin(ux) M. Boie
Hello. Now I understand why I was not clear. From what I understood, NOT VALID feature will not allow for the CHECK to be used in queries. So, for partitioning, my goal, is critical that the CHECK condition to be used. I hope I make myself clear now: I want a possibility to add a CHECK that wi

[GENERAL] Re: [GENERAL] Forcefully adding a CHECK constrained

2012-05-27 Thread Catalin(ux) M. Boie
Hello. Thanks for the answer. I really want to avoid reading the whole table. It is too expensive, and with the proposed feature will be not needed. I think is much faster to forcefully add the check if you know the range of data. What do you think? -- Catalin(ux) M. BOIE http://kernel.embedr