Re: Add jsonlog log_destination for JSON server logs - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Add jsonlog log_destination for JSON server logs
Date
Msg-id CAM-w4HPvcsAe=i5=dM3SFqFO7a_Ua4Y-=xzb_cNh-vbUCY1BRA@mail.gmail.com
Whole thread Raw
In response to Re: Add jsonlog log_destination for JSON server logs  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Add jsonlog log_destination for JSON server logs
List pgsql-hackers
Fwiw I was shocked when I saw the t/f T/F kluge when I went to work on
jsonlogging. That's the kind of dead-end short-sighted hack that just
lays traps and barriers for future hackers to have to clean up before
they can do the work they want to do.

Please just put a "format" field (or "channel" field -- the logging
daemon doesn't really care what format) with a list of defined formats
that can easily be extended in the future. If you want to steal the
high bit for "is last" and only allow 128 values instead of 256 so be
it.



pgsql-hackers by date:

Previous
From: "wangsh.fnst@fujitsu.com"
Date:
Subject: RE: drop tablespace failed when location contains .. on win32
Next
From: Michael Paquier
Date:
Subject: Re: drop tablespace failed when location contains .. on win32