Increasing the length of pg_stat_activity.current_query...

From: Sean Chittenden <sean(at)chittenden(dot)org>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Increasing the length of pg_stat_activity.current_query...
Date: 2004-11-06 19:11:24
Message-ID: A6BD0878-3027-11D9-9442-000A95C705DC@chittenden.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2004-11-06 19:17:29 Re: Documentation on PITR still scarce
Previous Message Andrew Dunstan 2004-11-06 18:35:30 cygwin build failure