Re: pg_stat_activity.application_name

From: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_stat_activity.application_name
Date: 2009-07-20 17:44:25
Message-ID: 3073cc9b0907201044u62130a48q8e12fea635a15671@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jul 17, 2009 at 9:58 AM, Kevin
Grittner<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
>
>> A facility to show it in the logs (via log_line_prefix probably)
>> would also be useful.
>
> Agreed.
>

ah! that seems a lot more useful. at least, i currently use logs to
identify malformed or bad-performant queries with that i will know
from what webpage they came

--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stefan Kaltenbrunner 2009-07-20 18:00:00 Re: [PATCH v4] Avoid manual shift-and-test logic in AllocSetFreeIndex
Previous Message Tom Lane 2009-07-20 17:16:49 Re: [PATCH] SE-PgSQL/tiny rev.2193