Re: DROP COLUMN - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: DROP COLUMN
Date
Msg-id GNELIHDDFBOCMGBFGEFOCEDFCDAA.chriskl@familyhealth.com.au
Whole thread Raw
In response to Re: DROP COLUMN  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> Hannu Krosing <hannu@tm.ee> writes:
> > All backend functions would still use real attnum's. And I doubt that
> > backend will ever work though system views.
> > Adding them should touch _only_ CREATE TABLE, ADD COLUMN, DROP COLUMN
> > plus the system views and possibly output from SELECT(*), if we allow
> > logical reordering of columns by changing attlognum.
>
> Hmm.  That last point is attractive enough to make it interesting to do.
>
> Christopher, you're the man doing the legwork ... what do you think?
> Offhand I'd think that expansion of "SELECT *" and association of
> column aliases to specific columns would be the two places that would
> need work to support attlognum; but we know they're both broken anyway
> by introduction of dropped columns.

Sure you don't want me to submit a working patch for DROP COLUMN first and
then do it after?

It wouldn't even cause any backward compatibility problems would it?  Older
clients would just order the columns by attnum...

Chris



pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: CREATE CONVERSION mostly works now
Next
From: Tatsuo Ishii
Date:
Subject: preventing encoding conversion while starting up