| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Davin Shearer <davin(at)apache(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Emitting JSON to file using COPY TO |
| Date: | 2023-12-06 16:19:19 |
| Message-ID: | 70c67e2a-f775-4d27-a5c4-dddaca67cedf@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On 12/6/23 10:44, Tom Lane wrote:
> Joe Conway <mail(at)joeconway(dot)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?
The concept is narrowly scoped enough that I think we are homing in on
the final patch.
> 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.
I will devise some kind of test and report back. I suppose something
with many rows and many narrow columns comparing time to COPY
text/csv/json modes would do the trick?
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2023-12-06 16:19:54 | Re: Emitting JSON to file using COPY TO |
| Previous Message | Estevan Rech | 2023-12-06 16:16:11 | Re: Delete Account |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2023-12-06 16:19:54 | Re: Emitting JSON to file using COPY TO |
| Previous Message | Nathan Bossart | 2023-12-06 16:18:39 | Re: Clean up some signal usage mainly related to Windows |