pg.ddx.io  pgsql-general@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Joe Conway <mail@joeconway.com>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: Davin Shearer <davin@apache.org>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Emitting JSON to file using COPY TO
Date: Wed, 06 Dec 2023 10:44:19 -0500
Message-ID: <1104915.1701877459@sss.pgh.pa.us> (raw)
In-Reply-To: <bbf922c5-f571-483e-a2c6-2730b02183fe@joeconway.com>
References: <CALvfUkBxTYy5uWPFVwpk_7ii2zgT07t3d-yR_cy4sfrrLU=kcg@mail.gmail.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>
	<CALvfUkAbj4Bwg0FjYpvj0-zddcetWg1Sejt=OGBTDskbqOFS_A@mail.gmail.com>
	<46cc4507-a0d9-4044-b2ce-5a8bca8015c0@joeconway.com>
	<CALvfUkD8+bcNs1cYeU3wK9YsyZ7zUjs2aTxO+++Vq7zKeUE7+w@mail.gmail.com>
	<2554e520-e103-8978-dcb5-807dfeb77402@dunslane.net>
	<cb1f118c-4698-4451-9ba9-dd8595f06c37@joeconway.com>
	<926ff917-8371-40ec-b5e6-ab7b0e09bdc5@joeconway.com>
	<315b81d4-4b67-7828-0355-3808cd14acd1@dunslane.net>
	<7a60faf6-e7f1-419d-aee6-10a78ea2fe81@joeconway.com>
	<2e7ff718-895d-83fc-46f7-be25e23b23b4@dunslane.net>
	<! bbf922c5-f571-483e-a2c6-2730b02183fe@joeconway.com>

Joe Conway <mail@joeconway.com> writes:
> I believe this is ready to commit unless there are further comments or 
> objections.

I thought we were still mostly at proof-of-concept stage?

In particular, has anyone done any performance testing?
I'm concerned about that because composite_to_json() has
zero capability to cache any metadata across calls, meaning
there is going to be a large amount of duplicated work
per row.

			regards, tom lane





view thread (163+ messages)  latest in thread

Message-ID: <1104915.1701877459@sss.pgh.pa.us>
Permalink:  ../1104915.1701877459@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1104915.1701877459@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, mail@joeconway.com, andrew@dunslane.net, davin@apache.org, pgsql-hackers@postgresql.org
  Subject: Re: Emitting JSON to file using COPY TO
  In-Reply-To: <1104915.1701877459@sss.pgh.pa.us>

* 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