Re: wrong results due to qual pushdown

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: tender wang <tndrwang(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: wrong results due to qual pushdown
Date: 2023-03-06 15:12:06
Message-ID: 3351639.1678115526@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

tender wang <tndrwang(at)gmail(dot)com> writes:
> It looks wrong that the qual (e.g ((l_suppkey IS NOT NULL) OR
> (getdatabaseencoding() !~~ CASE WHEN ($0 OR NULL::boolean) THEN NULL::text
> ELSE NULL::text END))) is pushdown.

I think this is the same issue reported at [1].

regards, tom lane

[1] https://www.postgresql.org/message-id/0b819232-4b50-f245-1c7d-c8c61bf41827%40postgrespro.ru

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Matthias van de Meent 2023-03-06 15:21:47 Re: Combine pg_walinspect till_end_of_wal functions with others
Previous Message Melanie Plageman 2023-03-06 15:09:24 Re: pg_stat_bgwriter.buffers_backend is pretty meaningless (and more?)