Re: pg_group_name_index corrupt? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_group_name_index corrupt?
Date
Msg-id 19637.957735764@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_group_name_index corrupt?  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> An --enable-syslog switch will be in the next release unless someone
> protests.

Seems reasonable.

>> Good question.  Before we standardize on that, however, some testing
>> might be in order.  I haven't tried stuffing multimegabyte querytree
>> dumps into syslog ... will it work?  On how many platforms?

> It's debatable whether these sort of things are appropriate for syslog,
> though. Who cares about the parse tree the next day?

Yeah.  We really need multiple log destinations to do this right.
Tim Holloway had some ideas about that last year, which I thought were
overkill at the time, but I'm beginning to see his point...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: You're on SecurityFocus.com for the cleartext passwords.
Next
From: Tom Lane
Date:
Subject: Re: You're on SecurityFocus.com for the cleartext passwords.