Re: BUG #17826: An assert failed in /src/backend/optimizer/util/var.c

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: xinwen(at)stu(dot)scu(dot)edu(dot)cn, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17826: An assert failed in /src/backend/optimizer/util/var.c
Date: 2023-03-17 03:11:39
Message-ID: CAApHDvrzEw6p7W_CDgGw1raP1WpUAp5sc7BiYC4CwWkeY9mPhw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, 17 Mar 2023 at 07:59, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> > OK, patch attached.
>
> This looks good to me. As a matter of style, I'd capitalize the
> enum constant names, but I think it's OK otherwise.

Thanks. I had been doing a bit more work on it and it looks very
slightly different from when you saw it. Agreed with the capitals in
the enum values.

I also found had to disallow subqueries in the WindowFunc. That
required a subplan check inside find_window_run_conditions().

I kinda also wanted to do the attached so that the logic to push or
not to push was more centralised. I just couldn't figure out exactly
why we don't push down pseudoconstant quals, therefore, was unable to
document that sufficiently in the header comment in
qual_is_pushdown_safe(). I thought we might as well talk about that
while on the topic as what I've just committed does not really take
any measures to explain it.

The attached patch is graded for the assistance of discussion only.

David

Attachment Content-Type Size
slightly_neater_qual_is_pushdown_safe.patch application/octet-stream 3.4 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2023-03-17 03:34:14 Re: BUG #17826: An assert failed in /src/backend/optimizer/util/var.c
Previous Message PG Bug reporting form 2023-03-17 03:10:49 BUG #17851: RHEL 8 GIS packages missing from common