Re: Proposal: More structured logging
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Ronan Dunklau <ronan.dunklau@aiven.io>
Cc: Julien Rouhaud <rjuju123@gmail.com>, Justin Pryzby <pryzby@telsasoft.com>, Alvaro Herrera <alvherre@alvh.no-ip.org>, pgsql-hackers@lists.postgresql.org
Date: 2022-01-27T07:15:01Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix ruleutils.c's dumping of whole-row Vars in more contexts.
- 43c2175121c8 15.0 cited
On Tue, Jan 18, 2022 at 06:46:03AM +0100, Ronan Dunklau wrote: > Hum, there was a missing import in csvlog.c from the fix above. Sorry about > that. +<!-- Don't forget to also update file_fdw.sgml if you change this table definition --> <programlisting> You are also forgetting that the table listing all the jsonlog fields needs a refresh with this new key called "tags", and that it has a JSON object underneath. If you want to test all the formats supported by logging_destination, wouldn't this stuff be better if tested through TAP with logging_destination set with csvlog, jsonlog and stderr? This is lacking coverage for csvlog.c and jsonlog.c, paths touched by your patch. -- Michael