select + order by

Started by Tatsuo Ishiiover 26 years ago6 messages
#1Tatsuo Ishii
t-ishii@sra.co.jp

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

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Tatsuo Ishii (#1)
Re: [HACKERS] select + order by

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

#3Tatsuo Ishii
t-ishii@sra.co.jp
In reply to: Tom Lane (#2)
Re: [HACKERS] select + order by

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

#4Bruce Momjian
maillist@candle.pha.pa.us
In reply to: Tatsuo Ishii (#3)
Re: [HACKERS] select + order by

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, Pennsylvania 19026
#5Noname
jwieck@debis.com
In reply to: Bruce Momjian (#4)
Re: [HACKERS] select + order by

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) #

#6Tatsuo Ishii
t-ishii@sra.co.jp
In reply to: Noname (#5)
Re: [HACKERS] select + order by

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