Re: Refactoring syslogger piping to simplify adding new log destinations

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
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:50:17
Message-ID: 19680.1562799017@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2019-07-10 22:54:12 Re: Refactoring syslogger piping to simplify adding new log destinations
Previous Message Tom Lane 2019-07-10 22:48:16 Re: [sqlsmith] Crash in mcv_get_match_bitmap