| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Joe Conway <mail(at)joeconway(dot)com>, 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:28:59 |
| Message-ID: | 1110690.1701880139@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 2023-12-06 We 10:44, Tom Lane wrote:
>> 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.
> Yeah, that's hard to deal with, too, as it can be called recursively.
Right. On the plus side, if we did improve this it would presumably
also benefit other callers of composite_to_json[b].
> OTOH I'd rather have a version of this that worked slowly than none at all.
It might be acceptable to plan on improving the performance later,
depending on just how bad it is now.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2023-12-06 16:33:49 | Re: Emitting JSON to file using COPY TO |
| Previous Message | Sehrope Sarkuni | 2023-12-06 16:28:33 | Re: Emitting JSON to file using COPY TO |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2023-12-06 16:33:49 | Re: Emitting JSON to file using COPY TO |
| Previous Message | Tristan Partin | 2023-12-06 16:28:49 | Re: Clean up some signal usage mainly related to Windows |