From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
---|---|
To: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: logging as inserts |
Date: | 2005-03-02 04:44:04 |
Message-ID: | 200503012344.04582.xzilla@users.sourceforge.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tuesday 01 March 2005 18:16, Gavin Sherry wrote:
> On Tue, 1 Mar 2005, Joshua D. Drake wrote:
> > Hello,
> >
> > I am looking at having one of our guys write up the code to allow
> > logging as insert statements. I have a couple of questions.
> >
> > What would we like the postgresql.conf option to be? I was thinking
> > log_statements_as_inserts = (t/f)
> >
> > However I thought that was getting a little silly. Also do we want
> > to allow logging as inserts for all options? There is a lot of different
> > types of logging we can do.
>
> Seems to me that a better approach is a script which, given the log file
> format, is able to parse and allow the user to format the insert
> themselves.
>
Doesn't the Practical Query Analysis project already do this? (It's up on
pgfoundry for anyone interested)
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Treat | 2005-03-02 05:12:41 | Re: mysterious log output |
Previous Message | Bruce Momjian | 2005-03-02 04:31:19 | Re: snprintf causes regression tests to fail |