MIME-Version: 1.0
References: <CALvfUkBxTYy5uWPFVwpk_7ii2zgT07t3d-yR_cy4sfrrLU=kcg@mail.gmail.com>
 <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>
 <b604b474-e2b2-4ba0-bc60-fd0cbc05cfc9@joeconway.com> <9c77b6fa-ee88-b2e6-0fa7-4fc81721da35@dunslane.net>
 <c30fc5da-0348-4e44-b699-804ccbdcfc36@joeconway.com> <41dcba92-1075-e5e5-cb99-36711abf6cec@dunslane.net>
 <bcbb2a04-5df3-49f2-b304-28ae8edc5189@joeconway.com> <CALvfUkB2QtG-BXsTwjoLO8ZYUsNFytqjPvZex8stQ0r_qNM7HQ@mail.gmail.com>
 <5c84b70b-ba18-c45d-dbbe-612fa229b2ce@dunslane.net> <CALvfUkDxgTppjy-Q_i2znakMFp2vrJdPUEJNyGTL2LcZBOWV6A@mail.gmail.com>
 <cbd65026-d79c-40b1-8be3-10e1db2fc092@joeconway.com> <398c22f6-4299-4b17-80bf-2f14f4afd592@joeconway.com>
In-Reply-To: <398c22f6-4299-4b17-80bf-2f14f4afd592@joeconway.com>
From: Davin Shearer <davin@apache.org>
Date: Tue, 5 Dec 2023 12:43:31 -0500
Message-ID: <CALvfUkAbj4Bwg0FjYpvj0-zddcetWg1Sejt=OGBTDskbqOFS_A@mail.gmail.com>
Subject: Re: Emitting JSON to file using COPY TO
To: PostgreSQL-development <pgsql-hackers@postgresql.org>
Cc: Andrew Dunstan <andrew@dunslane.net>, Joe Conway <mail@joeconway.com>
Content-Type: multipart/alternative; boundary="0000000000008d1f06060bc6c67d"
Archived-At: <https://www.postgresql.org/message-id/CALvfUkAbj4Bwg0FjYpvj0-zddcetWg1Sejt%3DOGBTDskbqOFS_A%40mail.gmail.com>
Precedence: bulk

--0000000000008d1f06060bc6c67d
Content-Type: text/plain; charset="UTF-8"

Thanks for the wayback machine link Andrew.  I read it, understood it, and
will comply.

Joe, those test cases look great and the outputs are the same as `jq`.

As for forward slashes being escaped, I found this:
https://stackoverflow.com/questions/1580647/json-why-are-forward-slashes-escaped
.

Forward slash escaping is optional, so not escaping them in Postgres is
okay.   The important thing is that the software _reading_ JSON interprets
both '\/' and '/' as '/'.

--0000000000008d1f06060bc6c67d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks for the wayback machine link Andrew.=C2=A0 I read i=
t, understood it, and will comply.<div><br></div><div>Joe, those test cases=
 look great and the outputs are the same as `jq`.</div><div><br></div><div>=
As for forward slashes being escaped, I found this:=C2=A0<a href=3D"https:/=
/stackoverflow.com/questions/1580647/json-why-are-forward-slashes-escaped">=
https://stackoverflow.com/questions/1580647/json-why-are-forward-slashes-es=
caped</a>.</div><div><br></div><div>Forward slash escaping is optional, so =
not escaping them in Postgres is okay. =C2=A0 The important thing is that t=
he software _reading_ JSON interprets both &#39;\/&#39; and &#39;/&#39; as =
&#39;/&#39;.</div></div>

--0000000000008d1f06060bc6c67d--