BUG #14617: Stetement terminator stored in pg_stat_statements

From: buschmann(at)nidsa(dot)net
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #14617: Stetement terminator stored in pg_stat_statements
Date: 2017-04-10 14:57:02
Message-ID: 20170410145702.25934.20733@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 14617
Logged by: Hans Buschmann
Email address: buschmann(at)nidsa(dot)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.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message julien.vacassoulis 2017-04-10 15:42:22 BUG #14618: pg_repack - waiting for 1 transactions to finish
Previous Message balazs 2017-04-10 08:27:37 BUG #14616: error message without schema