From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
---|---|
To: | jwieck(at)debis(dot)com (Jan Wieck) |
Cc: | maillist(at)candle(dot)pha(dot)pa(dot)us (Bruce Momjian), t-ishii(at)sra(dot)co(dot)jp, tgl(at)sss(dot)pgh(dot)pa(dot)us, hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] select + order by |
Date: | 1999-05-18 01:47:31 |
Message-ID: | 199905180147.KAA17929@srapc451.sra.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>> > > > select usename as aaa from pg_user order by usename;
>> > > > will produce 2 column names: "aaa" and "usename". Is this normal?
>> > >
>> > > No. I am not seeing it here with sources from 12 May. I am guessing
>> > > this has something to do with Jan's recent fixes for group by/order by
>> > > rewrites. Do you see it when you use a plain table, rather than a view?
>> >
>> > I see it with a plain table too.
>>
>> I just did a make clean, initdb, etc, and got:
>>
>> test=> select usename as aaa from pg_user order by usename;
>> aaa
>> --------
>> postgres
>> (1 row)
>>
>> Looks good to me.
>
> Yes, latest changes require a clear, intidb due to changes in
> the node out/read functions.
Getting latest sources and doing initdb solved the problem.
Thanks and sorry for the confusion.
---
Tatsuo Ishii
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1999-05-18 02:32:35 | Current TODO list |
Previous Message | Tom Lane | 1999-05-17 22:10:25 | Re: [HACKERS] DROP TABLE leaks file descriptors |