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

From Andrew Dunstan
Subject Re: Emitting JSON to file using COPY TO
Date
Msg-id 57db4b6e-51ba-4984-9343-bc62a3ee0b7c@dunslane.net
Whole thread Raw
In response to Re: Emitting JSON to file using COPY TO  (jian he <jian.universality@gmail.com>)
Responses Re: Emitting JSON to file using COPY TO
List pgsql-hackers
On 2026-03-06 Fr 4:38 AM, jian he wrote:
> COPY (SELECT 1 UNION ALL SELECT 2) TO stdout WITH (format json);
>
> still fails with v25-0002, json_tupledesc_ready is not helpful.
> I think I figured it out. We need to use BlessTupleDesc in BeginCopyTo.
> Then let slot->tts_tupleDescriptor point to cstate->queryDesc->tupDesc
> in CopyToJsonOneRow
>
>   * CSV, text and json formats share the same TextLike routines except for the
>   * one-row callback.
> This comment is not useful, I want to delete it.
>
> CopyToTextLikeStart
> + /* JSON-specific initialization */
> + if (cstate->opts.format == COPY_FORMAT_JSON)
> + {
> + MemoryContext oldcxt;
> +
> + /* Allocate reusable JSON output buffer in long-lived context */
> + oldcxt = MemoryContextSwitchTo(cstate->copycontext);
> + initStringInfo(&cstate->json_buf);
> + MemoryContextSwitchTo(oldcxt);
> + }
> We ca just add
>
> cstate->json_buf = makeStringInfo();
>
> in BeginCopyTo.
>
> v25-0004-COPY-TO-JSON-build-JSON-per-column-support-colum.patch
> added several fields to the CopyToStateData.
> Actually, there is a simpler way (construct a new Tupdesc and let
> composite_to_json do the job), please see my v26-0004.
>

Yeah, I got some crashes using this, but reworked it a bit, and all now 
seems good. I was apparently mistaken about the supposed speedup, but 
the performance is steady.


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com

Attachment

pgsql-hackers by date:

Previous
From: "Jonathan Gonzalez V."
Date:
Subject: Re: pg_upgrade fails when extension_control_path is used
Next
From: Andrei Lepikhov
Date:
Subject: Re: Skipping schema changes in publication