On 27 February 2018 at 16:50, Greg Stark wrote:
> On 27 February 2018 at 02:04, Michael Paquier wrote:
>> On Mon, Feb 26, 2018 at 05:38:56PM +, Greg Stark wrote:
>>
>> Hm. I have just loaded jsonlog on a 9.6 and 10 instance where
>> log_checkpoints is enabled with this background worker whic
On Tue, Feb 27, 2018 at 04:50:24PM +, Greg Stark wrote:
> I would actually lean another way. If jsonlog opened *.json and wrote
> there then it could leave the output_to_server field unchanged. It
> does look like this might be a bit awkward with yet more of the static
> functions needing to be
On 27 February 2018 at 02:04, Michael Paquier wrote:
> On Mon, Feb 26, 2018 at 05:38:56PM +, Greg Stark wrote:
>> I tried loading the jsonlog module from
>> https://github.com/michaelpq/pg_plugins into Postgres 9.6.
>>
>> However it seems it resulted in logs only for session log messages but
>
On Mon, Feb 26, 2018 at 05:38:56PM +, Greg Stark wrote:
> I tried loading the jsonlog module from
> https://github.com/michaelpq/pg_plugins into Postgres 9.6.
>
> However it seems it resulted in logs only for session log messages but
> not any background worker log messages. We have log_checkp
I tried loading the jsonlog module from
https://github.com/michaelpq/pg_plugins into Postgres 9.6.
However it seems it resulted in logs only for session log messages but
not any background worker log messages. We have log_checkpoints set
but there were no log messages in the json log about checkpo
