Re:BUG #18221: Unexpected Query Result

From: Sergei Kornilov <sk(at)zsrv(dot)org>
To: PG Bug reporting form <noreply(at)postgresql(dot)org>
Cc: bajinsheng(at)u(dot)nus(dot)edu, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re:BUG #18221: Unexpected Query Result
Date: 2023-12-03 13:44:09
Message-ID: 8521741701611049@gf6ne5m4hitewrno.vla.yp-c.yandex.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hello

Using "distinct on" without specifying an explicit "order by" is unpredictable in itself. I'll quote from the manual:

> Note that the “first row” of each set is unpredictable unless ORDER BY is used to ensure that the desired row appears first.

Can you reproduce the unexpected behavior with explicit order by clause?

regards, Sergei

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jan Březina 2023-12-03 19:55:56 Re: BUG #18219: libpq does not take into consideration UNICODE define
Previous Message Ivan Trofimov 2023-12-02 20:56:43 Re: BUG #17948: libpq seems to misbehave in a pipelining corner case