Re: [PATCH] Increase the maximum value track_activity_query_size

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, v(dot)makarov(at)postgrespro(dot)ru, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] Increase the maximum value track_activity_query_size
Date: 2019-12-19 17:52:39
Message-ID: CA+Tgmobjp+cqjNW+397Ejbo=M8XNzykQPspfhbd39DVc8Wd7Wg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Dec 19, 2019 at 10:59 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Bruce Momjian <bruce(at)momjian(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2019-12-19 18:05:18 Re: [PATCH] Remove twice assignment with var pageop (nbtree.c).
Previous Message Robert Haas 2019-12-19 17:47:22 Re: WIP/PoC for parallel backup