Re: Getting NOT NULL constraint from pg_attribute

Andres Freund <andres(at)anarazel(dot)de> writes:
> And arguably there's a fair bit of redundancy in pg_attribute, just
> because it's convenient for tupledescs. Given that pg_attribute very
> commonly is the largest catalog table by far, that very well could use
> some attention. Without tupdescs in mind, there's really not much point
> for pg_attribute to repeat a good portion of pg_type again, for example,
> nor is attcacheoff really meaningful.

Agreed about attcacheoff, but I'm less sure that we can drop the
"redundant" info copied from pg_type. The sticking point there is
that somebody could drop a column, then drop the type the column had,
but you still need to be able to skip over values in that column.
So at least attlen and attalign are not removable.

regards, tom lane