From: | Rod Taylor <rbt(at)rbt(dot)ca> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: fix log_min_duration_statement logic error |
Date: | 2003-10-05 21:40:51 |
Message-ID: | 1065390050.23288.224.camel@jester |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
> Probably pretty long. I think the pg_stat_activity case really needs
> the "\n" because if not the query breaks the table output format. Not
I was actually thinking exactly the opposite. pg_stat_activity viewed in
pgadmin GUI is going to format the table perfectly fine, but with
everthing on one line it will be next to impossible to understand
anything complex.
I would imagine psql will also be easier to read using human placed \n's
rather than random ones at the terminal width.
Perhaps the environment I work in isn't the normal case, but usually if
I'm trying to track something down, it's the complex 10 table join,
multi-subselect report style query that someone in account management
just happens to be running but poorly formed.
> It is hard to understand how a tool would grab the query from the above
> log except to look for another TAG: entry and stop there.
Yup.. Same way you group entries by PID, then reset the PID the next
time you see a new connection formed with it.
From | Date | Subject | |
---|---|---|---|
Next Message | Fabrizio Mazzoni | 2003-10-05 21:44:41 | psql italian translation |
Previous Message | Marc G. Fournier | 2003-10-05 21:33:46 | Re: Open 7.4 items |