Re: BUG #17671: Query returns unexpected result

From: Kieran McCusker <kieran(dot)mccusker(at)gmail(dot)com>
To: niko(at)aku(dot)mx, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17671: Query returns unexpected result
Date: 2022-10-31 10:07:02
Message-ID: CAGgUQ6H2N7smAFE5=T8gaEjeggDrYHMTtRmWtAOwhrhYGkE+5w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

It's not a bug. Union removes duplicates. Use union all.

Kieran

On Mon, 31 Oct 2022, 10:03 PG Bug reporting form, <noreply(at)postgresql(dot)org>
wrote:

> The following bug has been logged on the website:
>
> Bug reference: 17671
> Logged by: Nikola Mirkov
> Email address: niko(at)aku(dot)mx
> PostgreSQL version: 12.12
> Operating system: Ubuntu 12.12-0ubuntu0.20.
> Description:
>
> Hey guys,
> When I run the following query:
> SELECT foo, bar
> FROM table1
> WHERE fk_id = 637
> AND utc > '2022-10-16'
> UNION
> SELECT foo, bar
> FROM table2
> WHERE fk_id = 637
> AND utc > '2022-10-16'
>
> I'm getting only one row per table. If I add the column "utc" to the list
> in
> SELECT, I get the expected result.
>
> Why is this happening?
>
> Thank you so much!
> Niko
>
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Japin Li 2022-10-31 10:40:56 Re: BUG #17671: Query returns unexpected result
Previous Message Dilip Kumar 2022-10-31 08:53:46 Re: BUG #17670: Logical Replication data may be lost on the subscription under certain scenarios