| From: | Bruce Momjian <pgman(at)candle(dot)pha(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:19:39 |
| Message-ID: | 200411061919.iA6JJdU24547@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Sean Chittenden wrote:
> 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
I think it is limited because the queries are stored in shared memory,
maybe.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-11-06 19:36:36 | Re: Using ALTER TABLESPACE in pg_dump |
| Previous Message | Bruce Momjian | 2004-11-06 19:18:57 | Re: cygwin build failure |