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

From Tom Lane
Subject Re: Increasing the length of pg_stat_activity.current_query...
Date
Msg-id 11111.1099770255@sss.pgh.pa.us
Whole thread Raw
In response to Increasing the length of pg_stat_activity.current_query...  (Sean Chittenden <sean@chittenden.org>)
Responses Re: Increasing the length of pg_stat_activity.current_query...  (Sean Chittenden <sean@chittenden.org>)
Re: Increasing the length of  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
Sean Chittenden <sean@chittenden.org> writes:
> Is there any reason the length of 
> pg_catalog.pg_stat_activity.current_query is capped at 255 characters?  

The reason for a limit is to avoid fragmentation of UDP messages.
I believe we've set it at 1K for 8.0, though, and if you are on
a platform with a higher message size limit you could raise it more.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Using ALTER TABLESPACE in pg_dump
Next
From: Sean Chittenden
Date:
Subject: Re: Increasing the length of pg_stat_activity.current_query...