Re: Bug in pg_stat_statements

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>
Cc: Sami Imseih <samimseih(at)gmail(dot)com>, Konstantin Knizhnik <knizhnik(at)garret(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Bug in pg_stat_statements
Date: 2025-10-28 17:13:30
Message-ID: 202510281706.nwefxxvc4xdb@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2025-Oct-26, Dmitry Dolgov wrote:

> > On Fri, Oct 24, 2025 at 07:04:59PM -0500, Sami Imseih wrote:
> > v4 corrects some code comments.
>
> The fix in the first patch looks good, thanks.

Yeah, I think this general idea is sensible. However, I think we should
take it one step further and just remove last_loc entirely. I think
this makes the code a bit clearer. How about the attached?

Regarding 0002, as I said on my reply to Michael I think this is a good
idea on principle, but I suggest to discuss that in a separate thread.
I would seek routine names that match the current ones in queryjumble.h
a little better though.

> P.S. Adding Álvaro as a commiter of the affected feature, maybe he will
> help us to apply the fix.

Thanks for doing that, I'd have not noticed the thread otherwise.

--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"Pero la cosa no es muy grave ..." (le petit Nicolas -- René Goscinny)

Attachment Content-Type Size
v5-0001-pg_stat_statements-Fix-handling-of-duplicate-cons.patch text/x-diff 9.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2025-10-28 17:21:15 Re: Feature: psql - display current search_path in prompt
Previous Message Tanzeel Khan 2025-10-28 17:09:35 Missing post create object access hook in CreateForeignTable ?