| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Sehrope Sarkuni <sehrope(at)jackdb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, David Fetter <david(at)fetter(dot)org> |
| Subject: | Re: Add jsonlog log_destination for JSON server logs |
| Date: | 2021-09-09 02:58:51 |
| Message-ID: | CAM-w4HPvcsAe=i5=dM3SFqFO7a_Ua4Y-=xzb_cNh-vbUCY1BRA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2021-09-09 03:44:45 | Re: drop tablespace failed when location contains .. on win32 |
| Previous Message | wangsh.fnst@fujitsu.com | 2021-09-09 02:35:52 | RE: drop tablespace failed when location contains .. on win32 |