Bruce Momjian wrote:
>
> Sorry to be commenting so late.
>
> We could do that CLUSTER way of making a new heap file, but we rejected
> that for DROP COLUMN, so I am not sure why we would use that for ALTER
> COLUMN. Can anyone think of a good reason?
>
> Clearly if the new data type is binary c
Sorry to be commenting so late.
We could do that CLUSTER way of making a new heap file, but we rejected
that for DROP COLUMN, so I am not sure why we would use that for ALTER
COLUMN. Can anyone think of a good reason?
Clearly if the new data type is binary compatible and it is just a
catalog ch
Hey guys,
I was just thinking about altering column type. Now, I'm not actually going
to implement it any time soon, but I'm just thinking about it!!!
One proposal was to introduce a new pg_attribute column called 'attlognum'
so changing a column would involve adding a new column, dropping the o
