Re: [PATCH] Increase the maximum value track_activity_query_size
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <bruce@momjian.us>, v.makarov@postgrespro.ru, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2019-12-19T17:52:39Z
Lists: pgsql-hackers
On Thu, Dec 19, 2019 at 10:59 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: > Bruce Momjian <bruce@momjian.us> writes: > > Good question. I am in favor of allowing a larger value if no one > > objects. I don't think adding the min/max is helpful. > > I think there are pretty obvious performance and memory-consumption > penalties to very large track_activity_query_size values. Who exactly > are we really helping if we let them set it to huge values? The original poster. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Increase the maximum value of track_activity_query_size.
- 814727858918 13.0 landed