Increase the maximum value of track_activity_query_size.
authorRobert Haas <rhaas@postgresql.org>
Tue, 7 Jan 2020 17:14:19 +0000 (12:14 -0500)
committerRobert Haas <rhaas@postgresql.org>
Tue, 7 Jan 2020 17:14:19 +0000 (12:14 -0500)
commit814727858918154bdde9dbdfb99c544b52eb8818
treea613095ce9853179a2cbdc0e40723ede639ba2ed
parent2bd0735b954b14dcfab85d57fc4a0c7f9826fbb1
Increase the maximum value of track_activity_query_size.

This one-line change provoked a lot of discussion, but ultimately
the consensus seems to be that allowing a larger value might be
useful to somebody, and probably won't hurt anyone who chooses
not to take advantage of the higher maximum limit.

Vyacheslav Makarov, reviewed by many people.

Discussion: http://postgr.es/m/7b5ecc5a9991045e2f13c84e3047541d@postgrespro.ru
src/backend/utils/misc/guc.c