Re: pg_stat_statements: duplicated external query texts with MSY2 - Mailing list pgsql-bugs

From Julien Rouhaud
Subject Re: pg_stat_statements: duplicated external query texts with MSY2
Date
Msg-id CAOBaU_bzpLSMK2APN7Tkcw+G=6Pqjco-95vqvtCaS-8s97Dndg@mail.gmail.com
Whole thread Raw
In response to pg_stat_statements: duplicated external query texts with MSY2  (legrand legrand <legrand_legrand@hotmail.com>)
Responses Re: pg_stat_statements: duplicated external query texts with MSY2  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Hello,

On Mon, Jun 8, 2020 at 11:28 PM legrand legrand
<legrand_legrand@hotmail.com> wrote:
>
> Hello,
>
> I met a stange behavior with testing pg_stat_statements (default setup) with pgbench on my MSYS2 build
> (PostgreSQL 13beta1 on x86_64-w64-mingw32, compiled by x86_64-w64-mingw32-gcc.exe (Rev2, Built by MSYS2 project)
9.2.0,64-bit).
 
>
> pgbench -i postgres
> pgbench -c20 -t5 postgres
>
> generates the attached pgss_query_texts.stat,
> where "BEGIN" and "UPDATE pgbench_accounts SET abalance = abalance + $1 WHERE aid = $2"
> appears 20 times ...
>
> It does not seem to appear on linux, and I'm not able to juge if its specific to this port, and if its always limited
...

Is the duplication only in the query text file?  Looking at the code
the query text part is stored holding a shared lwlock, so it seems
like an expected behavior (less overhead but might store duplicated
query text)



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #16490: We cannot able to access production database remotely
Next
From: Michael Paquier
Date:
Subject: Re: BUG #16484: pg_regress fails with --outputdir parameter