Re: Increasing the length of pg_stat_activity.current_query...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sean Chittenden <sean(at)chittenden(dot)org>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Increasing the length of pg_stat_activity.current_query...
Date: 2004-11-06 19:44:15
Message-ID: 11111.1099770255@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Sean Chittenden <sean(at)chittenden(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sean Chittenden 2004-11-06 19:52:03 Re: Increasing the length of pg_stat_activity.current_query...
Previous Message Tom Lane 2004-11-06 19:36:36 Re: Using ALTER TABLESPACE in pg_dump