Increasing the length of pg_stat_activity.current_query... - Mailing list pgsql-hackers

From Sean Chittenden
Subject Increasing the length of pg_stat_activity.current_query...
Date
Msg-id A6BD0878-3027-11D9-9442-000A95C705DC@chittenden.org
Whole thread Raw
Responses Re: Increasing the length of pg_stat_activity.current_query...  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: Increasing the length of pg_stat_activity.current_query...  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Is there any reason the length of 
pg_catalog.pg_stat_activity.current_query is capped at 255 characters?  
Why can't it be a pointer to the currently running query?

Seems silly to me and is a PITA to try and use as a debugging tool only 
to find out that the query in question, has a logical break right at 
character 255 so the query in pg_stat_query looks like it's the 
complete query, but it's not (extra foo at the end of the query is 
causing it to run dog slow, but it's difficult to see that without 
going to the logs and digging through them to find the problem 
statement).

Anyway, is there any good reason for this or can this be increased 
somehow?  -sc

-- 
Sean Chittenden



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: cygwin build failure
Next
From: Bruce Momjian
Date:
Subject: Re: cygwin build failure