Re: More efficient truncation of pg_stat_activity query strings

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: More efficient truncation of pg_stat_activity query strings
Date: 2017-09-15 12:25:09
Message-ID: CA+TgmoYFf7LSJfbRHAu84AJRfbW8hGvPAd9OQZ5M9+xU3KLgdQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Sep 14, 2017 at 2:03 AM, Andres Freund <andres(at)anarazel(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2017-09-15 12:28:47 Re: no test coverage for ALTER FOREIGN DATA WRAPPER name HANDLER ...
Previous Message Robert Haas 2017-09-15 12:20:00 Re: no test coverage for ALTER FOREIGN DATA WRAPPER name HANDLER ...