Re: [[BUG] pg_stat_statements crashes with var and non-var expressions in IN clause

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>
Cc: Sami Imseih <samimseih(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [[BUG] pg_stat_statements crashes with var and non-var expressions in IN clause
Date: 2026-01-19 23:12:15
Message-ID: aW66Tz76P_dr0WXi@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jan 19, 2026 at 10:24:41AM +0100, Dmitry Dolgov wrote:
> Yep, I concur the current approach is fine. What I was saying about
> adjusting newa->list_end is just an ideal and at the moment only
> hypothetical scenario, where we could deduce end location of the new
> list based on its nested elements. Currently there are no mechanism to
> achieve that, so maybe in the future.

Okay, applied that down to v18 after a second lookup and a tweak to
the proposed comment.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-01-19 23:21:19 Re: Add WALRCV_CONNECTING state to walreceiver
Previous Message Hannu Krosing 2026-01-19 23:07:56 Re: Patch: dumping tables data in multiple chunks in pg_dump