Re: Emitting JSON to file using COPY TO - Mailing list pgsql-general

From David G. Johnston
Subject Re: Emitting JSON to file using COPY TO
Date
Msg-id CAKFQuwa=tVQxe0m6tnW-BtLhsGJN0ympLP=WiP+bsbavQU2w4A@mail.gmail.com
Whole thread Raw
In response to Re: Emitting JSON to file using COPY TO  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-general
On Monday, November 27, 2023, Pavel Stehule <pavel.stehule@gmail.com> wrote:
Hi

po 27. 11. 2023 v 14:27 odesílatel David G. Johnston <david.g.johnston@gmail.com> napsal:
On Monday, November 27, 2023, Dominique Devienne <ddevienne@gmail.com> wrote:
There's even a JSON mode.
By miracle, would the JSON output mode recognize JSON[B] values, and avoid the escaping?

I agree there should be a copy option for “not formatted” so if you dump a single column result in that format you get the raw unescaped contents of the column. As soon as you ask for a format your json is now embedded so it is a value within another format and any structural aspects of the wrapper present in the json text representation need to be escaped.

Is it better to use the LO API for this purpose?  It is native for not formatted data. 

Using LO is, IMO, never the answer.  But if you are using a driver API anyway just handle the normal select query result.

David J.

pgsql-general by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: Emitting JSON to file using COPY TO
Next
From: CG
Date:
Subject: Re: Removing oids with pg_repack