On 2019-Jul-10, Tom Lane wrote:
> Alvaro Herrera 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
Alvaro Herrera 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.
Hi Sehrope,
On 2019-Jul-10, Sehrope Sarkuni wrote:
> While working on adding a new log_destination I noticed that the
> syslogger piping would need to be updated. At the moment both ends
> only handle stderr/csvlog as the pipe message header has a char
> "is_last" that is either t/f (stderr
Hi,
While working on adding a new log_destination I noticed that the
syslogger piping would need to be updated. At the moment both ends
only handle stderr/csvlog as the pipe message header has a char
"is_last" that is either t/f (stderr last, stderr partial) or T/F
(csvlog last, csvlog partial).