| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Björn Lundin <b(dot)f(dot)lundin(at)gmail(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Order by and timestamp SOLVED |
| Date: | 2020-03-17 14:05:01 |
| Message-ID: | 31986.1584453901@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
=?utf-8?Q?Bj=C3=B6rn_Lundin?= <b(dot)f(dot)lundin(at)gmail(dot)com> writes:
>> What happens if you use psql(9.4.15) to do sort query against 9.4.15 server?
> However AFTER I checked the bad sorting - sep/oct 2016 and early apr 2017
> With psql 9.4 I connected with psql 9.6 again.
> And now the sorting error is gone her too!
Boy ... I don't have any confidence in that answer. psql does not re-sort
data, nor does it have any way to affect what the server does. It seems
to me that if this actually is a version inconsistency problem, that's
a bug in itself.
I am starting to wonder though if you had psql's FETCH_COUNT option
active in one configuration and not the other, and if so whether that
could explain anything.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Don Seiler | 2020-03-17 14:35:51 | Re: Mixed Locales and Upgrading |
| Previous Message | Tom Lane | 2020-03-17 13:56:01 | Re: Mixed Locales and Upgrading |