Re: [HACKERS] BUG: pg_stat_statements query normalization issues with combined queries - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] BUG: pg_stat_statements query normalization issues with combined queries
Date
Msg-id 30593.1485529387@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] BUG: pg_stat_statements query normalization issues withcombined queries  (Craig Ringer <craig.ringer@2ndquadrant.com>)
List pgsql-hackers
Craig Ringer <craig.ringer@2ndquadrant.com> writes:
> On 27 Jan. 2017 14:34, "Tom Lane" <tgl@sss.pgh.pa.us> wrote:
>> "The same queryString may be passed to multiple invocations of
>> ProcessUtility when processing a query string containing multiple
>> semicolon-separated statements; one should use pstmt->stmt_location and
>> pstmt->stmt_len to identify the substring containing the current
>> statement.  Keep in mind also that some utility statements (e.g.,
>> CREATE SCHEMA) will recurse to ProcessUtility to process sub-statements,
>> often passing down the same queryString, stmt_location, and stmt_len
>> that were given for the whole statement."

> Much better wording. I like that.

OK, done that way.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Christoph Berg
Date:
Subject: Re: [HACKERS] One-shot expanded output in psql using \G
Next
From: David Fetter
Date:
Subject: Re: [HACKERS] One-shot expanded output in psql using \G