Обсуждение: select + order by
Hi, I have observed a strange behavior with current source tree. For example, select usename from pg_user order by usename; is ok. But select usename as aaa from pg_user order by usename; will produce 2 column names: "aaa" and "usename". Is this normal? --- Tatsuo Ishii
Tatsuo Ishii <t-ishii@sra.co.jp> writes: > But > 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? regards, tom lane
> > 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. --- Tatsuo Ishii
> > > 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. -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania19026
> > > > > 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. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #======================================== jwieck@debis.com (Jan Wieck) #
>> > > > 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