Re: column aliases

Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Did this get resolved somehow?
>> 
>> ... a more graphic demonstration is had by using a WHERE clause that
>> can produce multiple matches:
>> 
>> regression=# select * from pg_language p where p.oid < pg_language.oid;
>> lanname  | lanispl | lanpltrusted | lanplcallfoid | lancompiler
>> ----------+---------+--------------+---------------+-------------
>> internal | f       | f            |             0 | n/a
>> internal | f       | f            |             0 | n/a
>> C        | f       | f            |             0 | /bin/cc
>> internal | f       | f            |             0 | n/a
>> C        | f       | f            |             0 | /bin/cc
>> sql      | f       | f            |             0 | postgres
>> (6 rows)
>> 
>> What it looks like to me is that we have a bug in the expansion of '*'.
>> It should be generating columns for both the explicit and the implicit
>> FROM clause, but it's evidently deciding that it should only produce
>> output columns for the first one.

Looks like the behavior is still the same (except now it says
NOTICE:  Adding missing FROM-clause entry for table pg_language
as well).  I'm inclined to say we should change it, and am willing
to do the work if no one objects...
        regards, tom lane