| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Subject: | Re: [PATCH] OAuth: fix performance bug with stuck multiplexer events |
| Date: | 2025-08-08 21:31:49 |
| Message-ID: | CAOYmi+m6t7r3jvDH-vUmy+GS_ZhstnPViE6Hee8c_M=_ASM9hg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Aug 8, 2025 at 2:16 PM Dagfinn Ilmari Mannsåker
<ilmari(at)ilmari(dot)org> wrote:
> That's because encode_json has a prototype[1], which changes how the
> argument list is parsed: no longer just as a flat list of values like a
> normal function. Specifically, it has a prototype of '$', which means
> it only takes one argument, which is evaluated in scalar context. So
> the first example is a syntax error, but in the second example the
> parenthesised expression is the single argument. Becuse it's in scalar
> context, the comma is actually the scalar comma operator, not the list
> element separator, so the return value is the right-hand side of the
> comma (just like in C), not the length of the would-be list.
ron-swanson-throws-away-computer.gif
Well, thank you for the explanation. I'll make that change.
--Jacob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul A Jungwirth | 2025-08-08 21:46:01 | Re: Inline non-SQL SRFs using SupportRequestSimplify |
| Previous Message | Andres Freund | 2025-08-08 21:23:13 | Re: Broken ./configure checks for __cpuid() and __cpuidex() |