Re: Refactoring syslogger piping to simplify adding new log destinations - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Refactoring syslogger piping to simplify adding new log destinations
Date
Msg-id 19680.1562799017@sss.pgh.pa.us
Whole thread Raw
In response to Re: Refactoring syslogger piping to simplify adding new logdestinations  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Refactoring syslogger piping to simplify adding new logdestinations  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
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.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [sqlsmith] Crash in mcv_get_match_bitmap
Next
From: Alvaro Herrera
Date:
Subject: Re: Refactoring syslogger piping to simplify adding new logdestinations