From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | jd(at)commandprompt(dot)com |
Subject: | Re: logging as inserts |
Date: | 2005-03-03 17:24:05 |
Message-ID: | 200503030924.05395.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Josh,
> >>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)
Nope.
log_destination = 'inserts' #not a new GUC!
insert_columns = '%u,%d,%r,%p, ... %$'
#this new GUC would define a list of comma-seperated columns as escape codes
defined via the same code set as log_line_prefix. The only change would be
the addition of %$, which would symbolize the "statement" being logged.
I'd also assert that this option should log the inserts to a "stderr" and thus
take advantage of all of the redirection, rotation, etc that we now support
for stderr logging.
--
Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-03-03 19:23:25 | Re: logging as inserts |
Previous Message | Tom Lane | 2005-03-03 16:56:32 | Re: 8.0.X and the ARC patent |