pg.ddx.io pgsql-general@postgresql.org mailing list archive help / color / mirror / Atom feed From: Joe Conway <mail@joeconway.com>
To: Davin Shearer <davin@apache.org>
To: PostgreSQL-development <pgsql-hackers@postgresql.org>
To: Andrew Dunstan <andrew@dunslane.net>
Subject: Re: Emitting JSON to file using COPY TO
Date: Sun, 3 Dec 2023 20:14:31 -0500
Message-ID: <b604b474-e2b2-4ba0-bc60-fd0cbc05cfc9@joeconway.com> (raw )
In-Reply-To: <CALvfUkBKTr9WLAbHQYmwZ7SVp5_VDey1F1uCZtKL4+H1-WvyBw@mail.gmail.com >
References: <CALvfUkBxTYy5uWPFVwpk_7ii2zgT07t3d-yR_cy4sfrrLU=kcg@mail.gmail.com >
<fc1e39f8-274f-4be6-8a70-9fb0d9fe84a2@aklaver.com >
<CAFCRh-_LhP5Ln4-beVz=1pQ9VycU3hAxnJHXhPHZRmX0BSCVEQ@mail.gmail.com >
<CAFCRh--Vhx0105S7SWAYHGcVMTSRtbcoArDUGSbYSWRUGunW_g@mail.gmail.com >
<CAKFQuwZb3zaSqkOvGXRRLZEW61az+4xyHZ7tBPR91JfrcdCKvA@mail.gmail.com >
<3853387.1701096982@sss.pgh.pa.us >
<CAFCRh-_GdiUvjd5z5FfvTfhruOnYqBu163XU47zZE8RNATCJGQ@mail.gmail.com >
<3a98decf-3fe3-4b49-9b68-fda01338872c@sedlakovi.org >
<CALvfUkCq3pvkmniWEKZwkbA6hNNvkANF3OamMfhC170RgY+HJg@mail.gmail.com >
<24e3ee88-ec1e-421b-89ae-8a47ee0d2df1@joeconway.com >
<b22367ef-6ac1-e1c0-da05-0e760e1b7e29@dunslane.net >
<CALvfUkD9ZFUU2pe9RMPqdGaKXu5OZi5xzOiPokGhOoPJ56FgAw@mail.gmail.com >
<7117a356-916c-4cf3-bad8-861490e65dcf@joeconway.com >
<CALvfUkBKTr9WLAbHQYmwZ7SVp5_VDey1F1uCZtKL4+H1-WvyBw@mail.gmail.com >
(please don't top quote on the Postgres lists)
On 12/3/23 17:38, Davin Shearer wrote:
> " being quoted as \\" breaks the JSON. It needs to be \". This has been
> my whole problem with COPY TO for JSON.
>
> Please validate that the output is in proper format with correct quoting
> for special characters. I use `jq` on the command line to validate and
> format the output.
I just hooked existing "row-to-json machinery" up to the "COPY TO"
statement. If the output is wrong (just for for this use case?), that
would be a missing feature (or possibly a bug?).
Davin -- how did you work around the issue with the way the built in
functions output JSON?
Andrew -- comments/thoughts?
Joe
> On Sun, Dec 3, 2023, 10:51 Joe Conway <mail@joeconway.com
> <mailto:mail@joeconway.com>> wrote:
>
> On 12/3/23 10:31, Davin Shearer wrote:
> > Please be sure to include single and double quotes in the test
> values
> > since that was the original problem (double quoting in COPY TO
> breaking
> > the JSON syntax).
>
> test=# copy (select * from foo limit 4) to stdout (format json);
> {"id":2456092,"f1":"line with ' in it:
> 2456092","f2":"2023-12-03T10:44:40.9712-05:00"}
> {"id":2456093,"f1":"line with \\" in it:
> 2456093","f2":"2023-12-03T10:44:40.971221-05:00"}
> {"id":2456094,"f1":"line with ' in it:
> 2456094","f2":"2023-12-03T10:44:40.971225-05:00"}
> {"id":2456095,"f1":"line with \\" in it:
> 2456095","f2":"2023-12-03T10:44:40.971228-05:00"}
>
> --
> Joe Conway
> PostgreSQL Contributors Team
> RDS Open Source Databases
> Amazon Web Services: https://aws.amazon.com <https://aws.amazon.com ;
>
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
view thread (163+ messages) latest in thread
Message-ID: <b604b474-e2b2-4ba0-bc60-fd0cbc05cfc9@joeconway.com>
Permalink: ../b604b474-e2b2-4ba0-bc60-fd0cbc05cfc9@joeconway.com/
Also on: postgresql.org/message-id/b604b474-e2b2-4ba0-bc60-fd0cbc05cfc9@joeconway.com
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-general@postgresql.org
Cc: mail@joeconway.com, davin@apache.org, pgsql-hackers@postgresql.org, andrew@dunslane.net
Subject: Re: Emitting JSON to file using COPY TO
In-Reply-To: <b604b474-e2b2-4ba0-bc60-fd0cbc05cfc9@joeconway.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox