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

From Sean Chittenden
Subject Re: Increasing the length of pg_stat_activity.current_query...
Date
Msg-id 545E4BF8-302D-11D9-9442-000A95C705DC@chittenden.org
Whole thread Raw
In response to Re: Increasing the length of pg_stat_activity.current_query...  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses 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?
>
> 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.

I'm confused... UDP as in the UDP/IP?  RPC caps UDP messages at 8K and 
NFS over UDP often runs at 32K...  where is UDP used in the backend?  
-sc

-- 
Sean Chittenden



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Increasing the length of pg_stat_activity.current_query...
Next
From: Tom Lane
Date:
Subject: relative_path() seems overly complicated and buggy