Re: [HACKERS] WIP: Separate log file for extension - Mailing list pgsql-hackers

From Tomas Vondra
Subject Re: [HACKERS] WIP: Separate log file for extension
Date
Msg-id d9acbdc2-34ca-0443-cf18-4647e17957bb@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] WIP: Separate log file for extension  (Antonin Houska <ah@cybertec.at>)
Responses Re: [HACKERS] WIP: Separate log file for extension  (Antonin Houska <ah@cybertec.at>)
List pgsql-hackers

On 08/28/2017 11:23 AM, Antonin Houska wrote:
> Craig Ringer <craig@2ndquadrant.com> wrote:
> 
>> On 25 August 2017 at 15:12, Antonin Houska <ah@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?

regards

-- 
Tomas Vondra                  http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: [HACKERS] segment size depending *_wal_size defaults (wasincreasing the default WAL segment size)
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Red-Black tree traversal tests