Horton

Re: [PATCH] Increase the maximum value track_activity_query_size

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: 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>, Michael Paquier <michael@paquier.xyz>, 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-03T18:48:56Z
Lists: pgsql-hackers 
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.

			regards, tom lane

Commits

  1. Increase the maximum value of track_activity_query_size.