From: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: logging as inserts |
Date: | 2005-03-01 23:16:04 |
Message-ID: | Pine.LNX.4.58.0503021011470.3779@linuxworld.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
The reason I say this is that users are almost always going to want a
human readable log. As such, post processing the log outside of the
database system seems to make sense.
>
> Sincerely,
>
> Joshua D. Drake
Gavin
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2005-03-01 23:18:30 | Re: Where to see the patch queue (was Re: [PATCHES] Patch |
Previous Message | Tom Lane | 2005-03-01 23:15:49 | Re: [HACKERS] snprintf causes regression tests to fail |