Re: [HACKERS] More efficient truncation of pg_stat_activity querystrings - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [HACKERS] More efficient truncation of pg_stat_activity querystrings
Date
Msg-id 20170915204910.oxt55ayeft7nvedm@alap3.anarazel.de
Whole thread Raw
In response to Re: [HACKERS] More efficient truncation of pg_stat_activity query strings  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] More efficient truncation of pg_stat_activity query strings  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 2017-09-15 16:45:47 -0400, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> > Version correcting these is attached. Thanks!
> 
> I'd vote for undoing the s/st_activity/st_activity_raw/g business.
> That may have been useful while writing the patch, to ensure you
> found all the references; but it's just creating a lot of unnecessary
> delta in the final code, with the attendant hazards for back-patches.

I was wondering about that too (see [1]). My only concern is that some
extensions out there might be accessing the string expecting it to be
properly truncated. The rename at least forces them to look for the new
name...  I'm slightly in favor of keeping the rename, it doesn't seem
likely to cause a lot of backpatch pain.

Regards,

Andres Freund


[1] http://archives.postgresql.org/message-id/20170914060329.j7lt7oyyzquxiut6%40alap3.anarazel.de


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] More efficient truncation of pg_stat_activity query strings
Next
From: Nico Williams
Date:
Subject: Re: [HACKERS] COMMIT TRIGGERs, take n, implemented with CONSTRAINTTRIGGERS