Re: And what about that Debugfile?
От | Tom Lane |
---|---|
Тема | Re: And what about that Debugfile? |
Дата | |
Msg-id | 5723.991862721@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | And what about that Debugfile? (Peter Eisentraut <peter_e@gmx.net>) |
Список | pgsql-hackers |
Peter Eisentraut <peter_e@gmx.net> writes: > There is a "postgres" option -o which can redirect the server output to a > file. The postmaster output will still go to stderr. Does anyone recall > how this was supposed to be useful? That code is, um, ancient. I recall having seen comments to the effect that you were expected to do something like "-o /dev/ttyNN" to redirect the debug output of a particular backend to your console. There's even a field in the initial connection message to allow this to be specified conveniently --- but I believe we've disabled it for security reasons, since one doesn't really want random clients to be able to command the backend to write on an arbitrary filename. I can see some value in being able to separate the log output of one backend from the rest of 'em ... but given the security issues, it seems unlikely that anyone will ever again use the feature in the way it was intended. It needs to be rethunk. regards, tom lane
В списке pgsql-hackers по дате отправления: