Re: "order by" and "order by asc" returning different results on date field
| От | Tom Lane |
|---|---|
| Тема | Re: "order by" and "order by asc" returning different results on date field |
| Дата | |
| Msg-id | 28102.1526410793@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | "order by" and "order by asc" returning different results on date field (Rick Gentry <rick.gentry@zenus-biometrics.com>) |
| Ответы |
Re: "order by" and "order by asc" returning different results on date field
|
| Список | pgsql-bugs |
Rick Gentry <rick.gentry@zenus-biometrics.com> writes:
> I have a table that I'm using to log results from my system. It has a
> field "created timestamp default current_timestamp."
> Running the query "select * from tbl_log order by created asc;" works as
> expected.
> Running the query "select * from tbl_log order by created;" returns sorted
> chunks of 2000 records.
It's quite hard to believe that the ASC annotation affects anything;
it's easily proven that PG's parser creates identical parsetrees for those
two statements. I have to guess that there is some other effect involved
here.
To start with, what PG version is this, what do you mean exactly by
"sorted chunks", and what client-side code are you using? Can you
create a self-contained example of the misbehavior?
regards, tom lane
В списке pgsql-bugs по дате отправления: