| From: | Michael Richards <miker(at)scifair(dot)acadiau(dot)ca> |
|---|---|
| To: | hackers(at)postgresql(dot)org |
| Subject: | Suggestions |
| Date: | 1998-05-04 00:31:23 |
| Message-ID: | Pine.BSF.3.96.980503213104.27331C-100000@scifair.acadiau.ca |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi.
I have a suggestion. I would be interested in implementing it if ppl think
it is a good idea.
Why not have a default location where postgres writes its log files. The
current way of doing it seems to be a little klunky.
I have an either/or suggested fix.
a) add a switch to specify where the info and the errors files go,
/var/log/postgres/info and maybe /var/log/postgres/errors
b) write all the stuff to syslog
I like b better because it would allow remote logging. One could then use
the features of syslog to dump the stuff they want to know about to an
approprate log file. I believe this would also be more effective at making
sure messages get sent when the backend crashes. I have seen a few places
where the messages don't seem to get there because of buffering...
-Mike
| From | Date | Subject | |
|---|---|---|---|
| Next Message | The Hermit Hacker | 1998-05-04 00:50:10 | Re: [HACKERS] Suggestions |
| Previous Message | Gautam Thaker | 1998-05-03 15:18:39 | on patch for close_ps() func. in geo_ops.c |