| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Inoue(at)tpf(dot)co(dot)jp, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>, scrappy(at)hub(dot)org |
| Subject: | Re: pg_group_name_index corrupt? |
| Date: | 2000-05-07 21:42:44 |
| Message-ID: | 19637.957735764@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-05-07 21:53:12 | Re: You're on SecurityFocus.com for the cleartext passwords. |
| Previous Message | Peter Eisentraut | 2000-05-07 21:42:23 | Re: Passwords |