Re: pg_stat_statements and "IN" conditions - Mailing list pgsql-hackers

From Marcos Pegoraro
Subject Re: pg_stat_statements and "IN" conditions
Date
Msg-id CAB-JLwZkCXfuiX_vAAmXoiAnEKK9-yPSxADL3v8PFft6QcjczQ@mail.gmail.com
Whole thread Raw
In response to Re: pg_stat_statements and "IN" conditions  (Dmitry Dolgov <9erthalion6@gmail.com>)
Responses Re: pg_stat_statements and "IN" conditions
List pgsql-hackers
Em dom., 29 de jan. de 2023 às 09:24, Dmitry Dolgov <9erthalion6@gmail.com> escreveu:
> On Fri, Jan 27, 2023 at 08:15:29PM +0530, vignesh C wrote:
> The patch does not apply on top of HEAD as in [1], please post a rebased patch:

Thanks. I think this one should do the trick.

There is a typo on DOC part
+        and it's length is larger than <varname> const_merge_threshold </varname>,
+        then array elements will contribure nothing to the query identifier.
+        Thus the query will get the same identifier no matter how many constants

That "contribure" should be "contribute"

regards
Marcos 

pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: lockup in parallel hash join on dikkop (freebsd 14.0-current)
Next
From: Jim Jones
Date:
Subject: Re: Authentication fails for md5 connections if ~/.postgresql/postgresql.{crt and key} exist