| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | josh(at)agliodbs(dot)com |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, "Hogan, James F(dot) Jr(dot)" <JHogan(at)seton(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: audit table containing Select statements submitted |
| Date: | 2006-05-12 23:51:30 |
| Message-ID: | 44651F82.9060605@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Josh Berkus wrote:
> Tom,
>
>> This argument strikes me as nonsense. You've got a utility that's smart
>> enough to parse the very-free-format message bodies, but it's going to
>> be too confused by the log line prefix?
>
> Having tinkered a little with PQA, yes, actually. The issue is that the
> "message" text can easily be multi-line and contain a vast variety of
> special characters. The issue is figuring out where the prefix, the tag
> and the message begin and end. And our text log format makes that a PITA.
>
Hmmm... well why don't we add log_line_suffix :)
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-05-13 00:38:07 | Re: [GENERAL] Querying libpq compile time options |
| Previous Message | Joshua D. Drake | 2006-05-12 23:37:27 | Re: audit table containing Select statements submitted |