[BUGS] BUG #14617: Stetement terminator stored in pg_stat_statements - Mailing list pgsql-bugs

From buschmann@nidsa.net
Subject [BUGS] BUG #14617: Stetement terminator stored in pg_stat_statements
Date
Msg-id 20170410145702.25934.20733@wrigleys.postgresql.org
Whole thread Raw
Responses Re: [BUGS] BUG #14617: Stetement terminator stored in pg_stat_statements
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      14617
Logged by:          Hans Buschmann
Email address:      buschmann@nidsa.net
PostgreSQL version: 9.6.2
Operating system:   Windows x64
Description:

I recently observed that the statement terminator (the semicolon) is stored
as part of the query column in pg_stat_tables.

When used programmatically (from Web application) the same statement has no
query separator and generates a separate entry in pg_stat_statements.
I observed it with a query like:

refresh materialized view my_mat_view;

which occurred twice when used interactively and by the program.

In my opinion the semicolon should be strapped before normalizing the query
for entry into pg_stat_statements.


--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: balazs@obiserver.hu
Date:
Subject: [BUGS] BUG #14616: error message without schema
Next
From: julien.vacassoulis@gmail.com
Date:
Subject: [BUGS] BUG #14618: pg_repack - waiting for 1 transactions to finish