| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | 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:54 |
| Message-ID: | 19a5f9d8-bd1f-9e51-0f5b-510c1189a8a7@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On 2023-12-06 We 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?
>
> 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.
OTOH I'd rather have a version of this that worked slowly than none at all.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2023-12-06 16:21:03 | Re: PostgreSQL 12 error unrecognized configuration parameter zbx_tmp.wal_json_res |
| Previous Message | Joe Conway | 2023-12-06 16:19:19 | Re: Emitting JSON to file using COPY TO |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-12-06 16:26:35 | Re: Emitting JSON to file using COPY TO |
| Previous Message | Joe Conway | 2023-12-06 16:19:19 | Re: Emitting JSON to file using COPY TO |