| From: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
|---|---|
| To: | "David Arnold" <dar(at)xoe(dot)solutions> |
| Cc: | "Christophe Pettus" <xof(at)thebuild(dot)com>,"John W Higgins" <wishdev(at)gmail(dot)com>,pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Proposal: Adding json logging |
| Date: | 2018-04-17 11:55:21 |
| Message-ID: | 3af99fd2-8c51-4b94-9ce2-3ef5aedf47f9@manitou-mail.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
David Arnold wrote:
> Interesting, does that implicitly mean the whole log event would get
> transmitted as a "line" (with CRLF) in CSV.
To me it's implied by the doc at:
https://www.postgresql.org/docs/current/static/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-CSVLOG
> In the affirmative scenario, this then would work for a true streaming
> aggregator (if CSV was supported).
Assuming a real CSV parser tailing the log, there shouldn't be any trouble
with that.
Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Naylor | 2018-04-17 12:10:30 | remove quoting hacks and simplify bootscanner.l |
| Previous Message | Peter Eisentraut | 2018-04-17 11:16:27 | Re: Proposal: Adding json logging |