Re: [HACKERS] On Logging

2005-10-01 Thread Jim C. Nasby
On Fri, Sep 30, 2005 at 06:24:17PM -0700, David Fetter wrote: > How would per-backend logging work? I'd suggest having settings for a per-backend 'debug' logging mode that could be triggered either via a SQL command or a signal to the backend. It would be useful to be able to log this to a seperat

Re: [HACKERS] On Logging

2005-09-30 Thread David Fetter
On Fri, Sep 30, 2005 at 05:54:49PM -0500, Jim C. Nasby wrote: > On Mon, Sep 26, 2005 at 10:57:54AM -0700, Ron Mayer wrote: > > David Fetter wrote: > > >...log file formats in 8.0 > > > > > >* CSV > > >* YAML > > >* XML > > >* Piped logs, as Apache can do > > >* DB handle. I know this one will

Re: [HACKERS] On Logging

2005-09-30 Thread Jim C. Nasby
On Mon, Sep 26, 2005 at 10:57:54AM -0700, Ron Mayer wrote: > David Fetter wrote: > >...log file formats in 8.0 > > > >* CSV > >* YAML > >* XML > >* Piped logs, as Apache can do > >* DB handle. I know this one will be controversial. > >[...] > >1. Am I the only one who would wants an option fo

Re: [HACKERS] On Logging

2005-09-26 Thread David Fetter
On Mon, Sep 26, 2005 at 01:13:08PM -0400, Christopher Petrilli wrote: > On 9/26/05, David Fetter <[EMAIL PROTECTED]> wrote: > > I've run into something that concerns me. It's pretty much an 8.2 > > issue, but I'm hoping to stimulate some discussion on it. It's > > PostgreSQL's log files. Right n

Re: [HACKERS] On Logging

2005-09-26 Thread Tom Lane
Andreas Pflug <[EMAIL PROTECTED]> writes: > - query is truncated due to UDP restrictions. Are you confusing the logs with pg_stat_activity? regards, tom lane ---(end of broadcast)--- TIP 6: explain analyze is your friend

Re: [HACKERS] On Logging

2005-09-26 Thread Ron Mayer
David Fetter wrote: ...log file formats in 8.0 * CSV * YAML * XML * Piped logs, as Apache can do * DB handle. I know this one will be controversial. [...] 1. Am I the only one who would wants an option for machine-readable logs? I'd very much like a format that can be easily loaded into

Re: [HACKERS] On Logging

2005-09-26 Thread Andreas Pflug
Tom Lane wrote: Andreas Pflug <[EMAIL PROTECTED]> writes: - query is truncated due to UDP restrictions. Are you confusing the logs with pg_stat_activity? Not confused. I'm talking about the case where statement logging is enabled, I could have mentioned that... Regards, Andreas --

Re: [HACKERS] On Logging

2005-09-26 Thread Andreas Pflug
David Fetter wrote: Folks, I've run into something that concerns me. It's pretty much an 8.2 issue, but I'm hoping to stimulate some discussion on it. It's PostgreSQL's log files. Right now, they're (sometimes just barely ;) human-readable, but they take significant effort to parse. For exam

Re: [HACKERS] On Logging

2005-09-26 Thread Bruce Momjian
Interesting. I am thinking we could put markers like '|' in the log output, and then have some secondary process either remove them or add special formatting to match the requested output format. --- David Fetter wrote: > Fo

Re: [HACKERS] On Logging

2005-09-26 Thread Andrew Dunstan
David Fetter wrote: Simple logging is a default that should probably not change, but I'm thinking that for people who want to find something out from the logs, we could see about a kind of plugin architecture which would enable things like: * CSV * YAML * XML * Piped logs, as Apache can do *

Re: [HACKERS] On Logging

2005-09-26 Thread Christopher Petrilli
On 9/26/05, David Fetter <[EMAIL PROTECTED]> wrote: > I've run into something that concerns me. It's pretty much an 8.2 > issue, but I'm hoping to stimulate some discussion on it. It's > PostgreSQL's log files. Right now, they're (sometimes just barely ;) > human-readable, but they take signific

[HACKERS] On Logging

2005-09-26 Thread David Fetter
Folks, I've run into something that concerns me. It's pretty much an 8.2 issue, but I'm hoping to stimulate some discussion on it. It's PostgreSQL's log files. Right now, they're (sometimes just barely ;) human-readable, but they take significant effort to parse. For example, pqa, a very cleve