Greg Smith <[EMAIL PROTECTED]> writes:
> On Mon, 19 Feb 2007, Alvaro Herrera wrote:
>> Also, "sql" is not really a destination -- it is a format.

> A log file with a different name is another destination.  eventlog is 
> certainly a different format and it's sitting happily as an option there. 
> I haven't heard anyone make a useful argument yet as to how insert/sql 
> logs are any different than the current way that stderr, syslog, and 
> eventlog are all possibilities now for log_destination, each with their 
> own little quirks (and in the case of syslog, their own additional GUC 
> parameters).

Since the "sql" format doesn't make any sense for syslog or eventlog
output, I tend to agree that treating it as a destination is a
reasonable answer.  It's going to be a bit non-orthogonal no matter
which way we jump, but this seems like the most natural and useful
extension from where we are.  To me anyway ... YMMV ...

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Reply via email to