| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | ganeshmmahesh(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17068: Incorrect ordering of a particular row. |
| Date: | 2021-06-22 13:46:16 |
| Message-ID: | CAApHDvoKk=NO7H6p8UNjSXbio8vq9yUjZhHO_Xr=C14WMs9i+A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, 23 Jun 2021 at 01:26, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> If you change the SELECT list to output alias3::text, there's a
> different value there:
Yeah, if I change it to ORDER BY alias3.lastname, nullnamesb.id;
instead of ORDER BY alias3.*, nullnamesb.id; then the tie break using
btint4fastcmp() is called more often. It's also getting called with
the missing 4s which I mentioned upthread.
See the two outputs. That points me towards something weird going on
in record_cmp().
David
| Attachment | Content-Type | Size |
|---|---|---|
| order_by_alias3_lastname.txt | text/plain | 2.6 KB |
| order_by_alias3_star.txt | text/plain | 2.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-06-22 14:00:22 | Re: BUG #17068: Incorrect ordering of a particular row. |
| Previous Message | Alvaro Herrera | 2021-06-22 13:42:18 | Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange |