Horton

Re: [PATCH] Increase the maximum value track_activity_query_size

Robert Haas <robertmhaas@gmail.com>

View thread View on postgr.es
From: Robert Haas <robertmhaas@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Jeff Janes <jeff.janes@gmail.com>, Andrew Dunstan <andrew.dunstan@2ndquadrant.com>, Tomas Vondra <tomas.vondra@2ndquadrant.com>, Robert Treat <rob@xzilla.net>, Nikolay Samokhvalov <samokhvalov@gmail.com>, Bruce Momjian <bruce@momjian.us>, Alexey Kondratov <a.kondratov@postgrespro.ru>, v.makarov@postgrespro.ru, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-01-07T17:21:26Z
Lists: pgsql-hackers 
On Sun, Jan 5, 2020 at 11:01 PM Michael Paquier <michael@paquier.xyz> wrote:
> Sounds like an agreement then.  The original patch documents the range
> in postgresql.conf.sample, which is fine by me as this is done for
> some parameters, and skips the part about doc/, which also matches
> with the surrounding effort for other parameters, so the whole looks
> fine seen from here.  Anybody willing to commit that?

Done. I didn't commit the postgresql.conf.sample change because:

(1) I think Bruce voted against it.

(2) It makes the line a little wide, and I'd rather not do that.

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

Commits

  1. Increase the maximum value of track_activity_query_size.