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

From Robert Haas
Subject Re: [PATCH] Increase the maximum value track_activity_query_size
Date
Msg-id CA+Tgmobjp+cqjNW+397Ejbo=M8XNzykQPspfhbd39DVc8Wd7Wg@mail.gmail.com
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  (Alexey Kondratov <a.kondratov@postgrespro.ru>)
List 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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: WIP/PoC for parallel backup
Next
From: Peter Geoghegan
Date:
Subject: Re: [PATCH] Remove twice assignment with var pageop (nbtree.c).