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

From Jeff Janes
Subject Re: [PATCH] Increase the maximum value track_activity_query_size
Date
Msg-id CAMkU=1w32sJ3xoCK+q6Kw05HcOWCsgCUZmgwnjWOsYYziN95Hg@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Increase the maximum value track_activity_query_size  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Tue, Dec 24, 2019 at 12:11 AM Robert Haas <robertmhaas@gmail.com> wrote:
On Sat, Dec 21, 2019 at 1:25 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > What is the overhead here except the memory consumption?
>
> The time to copy those strings out of shared storage, any time
> you query pg_stat_activity.

It seems like you're masterminding this, and I don't know why. It
seems unlikely that anyone will raise the value unless they have very
long queries, and if those people would rather pay the overhead of
copying more data than have their queries truncated, who are we to
argue?

+1

Cheers,

Jeff

pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: TAP testing for psql's tab completion code
Next
From: Tom Lane
Date:
Subject: Re: TAP testing for psql's tab completion code