Re: [HACKERS] More efficient truncation of pg_stat_activity query strings - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] More efficient truncation of pg_stat_activity query strings
Date
Msg-id CA+TgmoYFf7LSJfbRHAu84AJRfbW8hGvPAd9OQZ5M9+xU3KLgdQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] More efficient truncation of pg_stat_activity querystrings  (Andres Freund <andres@anarazel.de>)
Responses Re: [HACKERS] More efficient truncation of pg_stat_activity querystrings  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Thu, Sep 14, 2017 at 2:03 AM, Andres Freund <andres@anarazel.de> wrote:
> Here's a patch that implements that idea.

From the department of cosmetic nitpicking:

+     * All supported server-encodings allow to determine the length of a

make it possible to determine

+     * multi-byte character from it's first byte (not the case for client

its

this is not the case

+     * encodings, see GB18030). As st_activity always is stored using server

is always stored using a server

+     * pgstat_clip_activity() to trunctae correctly.

truncate

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


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

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] no test coverage for ALTER FOREIGN DATA WRAPPER nameHANDLER ...
Next
From: Amit Langote
Date:
Subject: Re: [HACKERS] no test coverage for ALTER FOREIGN DATA WRAPPER nameHANDLER ...