| From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
|---|---|
| To: | Antonin Houska <ah(at)cybertec(dot)at>, pgsql-hackers(at)postgresql(dot)org |
| Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Subject: | Re: WIP: Separate log file for extension |
| Date: | 2017-09-09 23:14:04 |
| Message-ID: | d9acbdc2-34ca-0443-cf18-4647e17957bb@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 08/28/2017 11:23 AM, Antonin Houska wrote:
> Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
>
>> On 25 August 2017 at 15:12, Antonin Houska <ah(at)cybertec(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-09-10 00:07:00 | Re: Red-Black tree traversal tests |
| Previous Message | Tomas Vondra | 2017-09-09 22:23:54 | Re: segment size depending *_wal_size defaults (was increasing the default WAL segment size) |