Re: ORDER BY TABLENAME, possible bug

From: Pantelis Theodosiou <ypercube(at)gmail(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: dv <udv(dot)mail(at)gmail(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: ORDER BY TABLENAME, possible bug
Date: 2016-11-18 22:35:18
Message-ID: CAE3TBxwNsfrHJc=XaTpZ3aq6=Z4PevcqQgQOi3wAh7mNB8pioA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, Oct 29, 2016 at 3:23 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
wrote:

> Hi
>
> 2016-10-29 14:13 GMT+02:00 dv <udv(dot)mail(at)gmail(dot)com>:
>
>> E.g. query:
>>
>> SELECT col1, col2, col3
>> FROM table1
>> ORDER BY table1
>>
>> Postgres uses col1 for ASC ordering, if we write "ORDER BY table1
>> DESC" then DESC-ordering. I'm not sure this is a bug, but didn't find
>> description for such behaviour.
>>
>
> It is not bug. Postgresql's table has fictive column with same name as
> tablename that is composite of all columns
>
>
>
Is this somewhere in the documentation? The only place I could find where
there is a hint of this use, is the Note in Row Constructors in
https://www.postgresql.org/docs/current/static/sql-expressions.html that
uses a table alias without the .* in an expression: ROW(t, 42)

Pantelis Theodosiou

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2016-11-18 22:48:42 Re: ORDER BY TABLENAME, possible bug
Previous Message David G. Johnston 2016-11-18 14:45:38 Re: BUG #14428: decode function don't return correct value when executed from agent's job or external program