Re: Bug in pg_stat_statements

Álvaro Herrera <alvherre@kurilemu.de>

From: Álvaro Herrera <alvherre@kurilemu.de>

To: Sami Imseih <samimseih@gmail.com>

Cc: Dmitry Dolgov <9erthalion6@gmail.com>, Konstantin Knizhnik <knizhnik@garret.ru>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2025-10-29T11:36:55Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

pg_stat_statements: Fix handling of duplicate constant locations
- b1635c166698 18.1 landed
- 16edc1b94fc2 19 (unreleased) landed

On 2025-Oct-28, Sami Imseih wrote:

> getting rid of last_loc makes sense because the list is sorted. I like
> this, definitely cleaner.
> 
> One minor comment is to change is to remove the "let's save it" but
> in the comments, as we are no longer saving a last_loc.

Ah, yeah, that's a good change.  I have pushed it now.

Thanks!

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"Entristecido, Wutra                     (canción de Las Barreras)
echa a Freyr a rodar
y a nosotros al mar"