No, that tests whether the particular tuple contains any null fields, not whether the whole table is declared NOT NULL.
regards, tom lane
Ok, thanks, that makes sense.
My question kind of remains though - does that mean that having any nulls in the tuple loses the ability to use the tupleDesc cache? and how much of a performance impact is this? I'm sure there's a good reason why you can't really use the cache if you have a null column, just was curious of the implications. Thanks again!
