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

From Tom Lane
Subject Re: [PATCH] Increase the maximum value track_activity_query_size
Date
Msg-id 30005.1578077336@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCH] Increase the maximum value track_activity_query_size  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [PATCH] Increase the maximum value track_activity_query_size  (Michael Paquier <michael@paquier.xyz>)
List 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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Greatest Common Divisor
Next
From: Robert Haas
Date:
Subject: Re: Assigning ROW variable having NULL value to RECORD type variabledoesn't give any structure to the RECORD variable.