Tomas Vondra <tomas.von...@2ndquadrant.com> wrote: > On 08/28/2017 11:23 AM, Antonin Houska wrote: > > Craig Ringer <cr...@2ndquadrant.com> wrote: > > > >> On 25 August 2017 at 15:12, Antonin Houska <a...@cybertec.at> wrote: > >> > >> How will this play with syslog? csvlog? etc? > > > > There's nothing special about csvlog: the LogStream structure has a > > "destination" field, so if particular extension wants this kind of output, > > it > > simply sets the LOG_DESTINATION_CSVLOG bit here. > > > > I assume Craig's point was more about CSVLOG requiring log_collector=on. > So what will happen if the PostgreSQL is started without the collector, > and an extension attempts to use LOG_DESTINATION_CSVLOG? Or will it > start a separate collector for each such extension?
The patch does not try to change this behavior. So there'll be no csvlog file and only the plain (not csv-formatted) message will be written to console. -- Antonin Houska Cybertec Schönig & Schönig GmbH Gröhrmühlgasse 26 A-2700 Wiener Neustadt Web: http://www.postgresql-support.de, http://www.cybertec.at -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
