Re: Refactoring syslogger piping to simplify adding new logdestinations
| От | Alvaro Herrera |
|---|---|
| Тема | Re: Refactoring syslogger piping to simplify adding new logdestinations |
| Дата | |
| Msg-id | 20190710225412.GA18449@alvherre.pgsql обсуждение исходный текст |
| Ответ на | Re: Refactoring syslogger piping to simplify adding new log destinations (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Refactoring syslogger piping to simplify adding new log destinations
|
| Список | pgsql-hackers |
On 2019-Jul-10, Tom Lane wrote: > Alvaro Herrera <alvherre@2ndquadrant.com> writes: > > Maybe we can use something like a shared memory queue, working in a > > similar way to wal_buffers -- where backends send over the shm queue to > > syslogger, and syslogger writes in order to the actual log file. > > No way that's going to be acceptable for postmaster output. Well, we can use both mechanisms simultaneously. Postmaster doesn't emit all that much output anyway, so I don't think that's a concern. And actually, we still need the pipes from the backend for the odd cases where third party code writes to stderr, no? -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: