| From: | Maciek Sakrejda <m(dot)sakrejda(at)gmail(dot)com> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | Davin Shearer <davin(at)apache(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Emitting JSON to file using COPY TO |
| Date: | 2023-12-02 18:50:12 |
| Message-ID: | CAOtHd0C+k8M1HYPubnH6J_7B5Eh5_nrun-n3fc9ZsSb_Tq9ZHA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Fri, Dec 1, 2023 at 11:32 AM Joe Conway <mail(at)joeconway(dot)com> wrote:
> 1. Is supporting JSON array format sufficient, or does it need to
> support some other options? How flexible does the support scheme need to be?
"JSON Lines" is a semi-standard format [1] that's basically just
newline-separated JSON values. (In fact, this is what
log_destination=jsonlog gives you for Postgres logs, no?) It might be
worthwhile to support that, too.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2023-12-02 21:53:20 | Re: Emitting JSON to file using COPY TO |
| Previous Message | Tom Lane | 2023-12-02 15:11:20 | Re: Emitting JSON to file using COPY TO |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rafael Thofehrn Castro | 2023-12-02 19:30:59 | Proposal: In-flight explain logging |
| Previous Message | Paul Jungwirth | 2023-12-02 18:41:01 | Re: SQL:2011 application time |