| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, jian he <jian(dot)universality(at)gmail(dot)com>, Erik Rijkers <er(at)xs4all(dot)nl>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: remaining sql/json patches |
| Date: | 2023-11-15 17:12:07 |
| Message-ID: | 20231115171207.wmngkznab7jlslwc@awork3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2023-11-15 09:11:19 -0800, Andres Freund wrote:
> On 2023-11-15 22:00:41 +0900, Amit Langote wrote:
> > > This causes a nontrivial increase in the size of the parser (~5% in an
> > > optimized build here), I wonder if we can do better.
> >
> > Hmm, sorry if I sound ignorant but what do you mean by the parser here?
>
> gram.o, in an optimized build.
Or, hm, maybe I meant the size of the generated gram.c actually.
Either is worth looking at.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2023-11-15 17:15:32 | Re: pg_basebackup check vs Windows file path limits |
| Previous Message | Andres Freund | 2023-11-15 17:11:19 | Re: remaining sql/json patches |