From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org, jd(at)commandprompt(dot)com |
Subject: | Re: logging as inserts |
Date: | 2005-03-03 21:02:29 |
Message-ID: | 200503031302.30032.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom,
> That seems a bit bizarre to me. The facility isn't a new log
> destination; what it is is a different way of formatting what's
> sent to the log.
It's not, but it functions like one. And ultimately, the destination *is*
someplace different; likely the DBA will be piping the log output to another
database somewhere.
> log_message_format = 'INSERT INTO mytab VALUES(%this, %that, ...);'
Yeah, good idea.
> I wonder whether this could be defined in a way that lets it replace
> log_line_prefix ... otherwise we have to think about the interaction of
> the two facilities.
Well, that's why I like the idea of using log_destination. It makes it clear
that log_line_prefix doesn't work if log_destination <> 'stderr'.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2005-03-03 21:03:11 | Re: unexpected and reproducable crash in pl/pgsql function |
Previous Message | Merlin Moncure | 2005-03-03 19:47:59 | unexpected and reproducable crash in pl/pgsql function |