| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, 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 19:48:52 |
| Message-ID: | 77312d02-9325-4f14-9fe0-2746c2ee12bc@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On 12/6/23 11:44, Nathan Bossart wrote:
> On Wed, Dec 06, 2023 at 10:33:49AM -0600, Nathan Bossart wrote:
>> (format csv)
>> Time: 12295.480 ms (00:12.295)
>> Time: 12311.059 ms (00:12.311)
>> Time: 12305.469 ms (00:12.305)
>>
>> (format json)
>> Time: 24568.621 ms (00:24.569)
>> Time: 23756.234 ms (00:23.756)
>> Time: 24265.730 ms (00:24.266)
>
> I should also note that the json output is 85% larger than the csv output.
I'll see if I can add some caching to composite_to_json(), but based on
the relative data size it does not sound like there is much performance
left on the table to go after, no?
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-12-06 20:20:46 | Re: Emitting JSON to file using COPY TO |
| Previous Message | Joe Conway | 2023-12-06 19:47:25 | Re: Emitting JSON to file using COPY TO |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2023-12-06 19:50:16 | Re: Bug in nbtree optimization to skip > operator comparisons (or < comparisons in backwards scans) |
| Previous Message | Joe Conway | 2023-12-06 19:47:25 | Re: Emitting JSON to file using COPY TO |