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

From Michael Paquier
Subject Re: [PATCH] Increase the maximum value track_activity_query_size
Date
Msg-id 20200106040117.GI3598@paquier.xyz
Whole thread Raw
In response to Re: [PATCH] Increase the maximum value track_activity_query_size  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCH] Increase the maximum value track_activity_query_size  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Fri, Jan 03, 2020 at 01:48:56PM -0500, Tom Lane wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> I vote for not trying to make this more complicated and just accepting
>> the original proposal. It's about a factor of ten increase over the
>> limit we have right now, which doesn't seem like enough to cause any
>> real breakage, and it should be enough to satisfy the majority of the
>> people who are unhappy with the current limit, and it is very little
>> work.
>
> +1 ... we've surely beaten this topic to death by now.

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?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: chenhj
Date:
Subject: Re:could not access status of transaction
Next
From: Justin Pryzby
Date:
Subject: Re: doc: alter table references bogus table-specific plannerparameters