Re: [PATCH] Increase the maximum value track_activity_query_size - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [PATCH] Increase the maximum value track_activity_query_size
Date
Msg-id CA+Tgmob=-phbXtOjSsOgh9_3m4KJ5F2Kq73fM-qaYACA2jUQ=w@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Increase the maximum value track_activity_query_size  (Michael Paquier <michael@paquier.xyz>)
Responses Re: [PATCH] Increase the maximum value track_activity_query_size  (Michael Paquier <michael@paquier.xyz>)
List 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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Removing pg_pltemplate and creating "trustable" extensions
Next
From: Tom Lane
Date:
Subject: Re: ERROR: attribute number 6 exceeds number of columns 5