On Friday, September 07, 2012 12:20 AM Amit Kapila wrote:
On Tue, Aug 28, 2012 at 6:40 AM, Amit Kapila wrote:
>> AFAICT during Update also, it doesn't contain useful. The only chance
it
>> would have contain something useful is when it goes for EvalPlanQual and
>> then again comes to check for c
On Tue, Aug 28, 2012 at 6:40 AM, Amit Kapila wrote:
> AFAICT during Update also, it doesn't contain useful. The only chance it
> would have contain something useful is when it goes for EvalPlanQual and
> then again comes to check for constraints. However these attributes get
> filled in heap_upd
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Tuesday, August 28, 2012 2:04 AM
Robert Haas writes:
>> Maybe, but in that case shouldn't referencing a system column chuck an
error?
> Yeah, possibly. I think none of them are populated with anything useful
> during INSERT checks (though OID mig
On Mon, Aug 27, 2012 at 1:34 PM, Tom Lane wrote:
> Robert Haas writes:
> > Maybe, but in that case shouldn't referencing a system column chuck an
> error?
>
> Yeah, possibly. I think none of them are populated with anything useful
> during INSERT checks (though OID might be an exception?). Les
Robert Haas writes:
> Maybe, but in that case shouldn't referencing a system column chuck an error?
Yeah, possibly. I think none of them are populated with anything useful
during INSERT checks (though OID might be an exception?). Less sure
about the state during UPDATE checks, though.
On Fri, Aug 24, 2012 at 10:38 AM, Tom Lane wrote:
> Chris Travers writes:
>> Table inheritance would be easier if there was a way to declare a
>> constraint such that it prevents insert for some rows on the parent
>> but not for a child and/or vice versa.
>
> FWIW, 9.2 adds support for constraint
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Friday, August 24, 2012 7:46 PM
Amit Kapila writes:
> From: pgsql-bugs-ow...@postgresql.org
> [mailto:pgsql-bugs-ow...@postgresql.org] On Behalf Of Tom Lane
>>> None of the system columns are set at the time check constraints are
>>> checked.
>> I
Chris Travers writes:
> Table inheritance would be easier if there was a way to declare a
> constraint such that it prevents insert for some rows on the parent
> but not for a child and/or vice versa.
FWIW, 9.2 adds support for constraints that only apply to the named
table and don't get inherite
On Fri, Aug 24, 2012 at 3:52 AM, Amit Kapila wrote:
> From: pgsql-bugs-ow...@postgresql.org
> [mailto:pgsql-bugs-ow...@postgresql.org] On Behalf Of Tom Lane
> Sent: Friday, August 24, 2012 10:33 AM
> Chris Travers writes:
>>> My guess is that tableoid is not known when the check constraint is
>>>
Amit Kapila writes:
> From: pgsql-bugs-ow...@postgresql.org
> [mailto:pgsql-bugs-ow...@postgresql.org] On Behalf Of Tom Lane
>> None of the system columns are set at the time check constraints are
>> checked.
> Is there any problem if set tableOID before calling ExecConstarints()?
Well, possibly
From: pgsql-bugs-ow...@postgresql.org
[mailto:pgsql-bugs-ow...@postgresql.org] On Behalf Of Tom Lane
Sent: Friday, August 24, 2012 10:33 AM
Chris Travers writes:
>> My guess is that tableoid is not known when the check constraint is
>> checked.
>None of the system columns are set at the time chec
Chris Travers writes:
> My guess is that tableoid is not known when the check constraint is
> checked.
None of the system columns are set at the time check constraints are
checked.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To mak
Hi;
I figured I would report this as well, primarily because people
getting into table inheritance may try to use this to solve the set
exclusion problem (i.e. partly required to prevent duplicate key
values in an inheritance tree). I see this as minor because I don't
see a lot of people using th
13 matches
Mail list logo
