Re: Refactoring syslogger piping to simplify adding new log destinations

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Sehrope Sarkuni <sehrope(at)jackdb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Refactoring syslogger piping to simplify adding new log destinations
Date: 2019-07-10 22:54:12
Message-ID: 20190710225412.GA18449@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2019-Jul-10, Tom Lane wrote:

> Alvaro Herrera <alvherre(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-07-10 22:59:27 Re: Refactoring syslogger piping to simplify adding new log destinations
Previous Message Tom Lane 2019-07-10 22:50:17 Re: Refactoring syslogger piping to simplify adding new log destinations