Re: [PATCH] OAuth: fix performance bug with stuck multiplexer events

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 20:52:09
Message-ID: CAOYmi+nUAU+eJx__j6Uhmn3QV2G6NTdbL-_OJA1YQmscmKZiqw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Aug 8, 2025 at 1:07 PM Dagfinn Ilmari Mannsåker
<ilmari(at)ilmari(dot)org> wrote:
> $ perl -MJSON::PP=encode_json -E 'say encode_json([1, 2, 3])'
> [1,2,3]
>
> $ perl -MJSON::PP=encode_json -E 'say encode_json([1 => (2, 3)])'
> [1,2,3]

I swear, this language.

But:

$ perl -MJSON::PP=encode_json -E 'say encode_json(1,2)'
Too many arguments for JSON::PP::encode_json at -e line 1, near "2)
$ perl -MJSON::PP=encode_json -E 'say encode_json((1,2))'
2

So what's going on there? (Google is not very helpful for these sorts
of Perl problems; I don't even know how to describe this.)

I had to revert the test for unrelated reasons [1], so if this is
indeed guaranteed to be safe then I can make the change in my next
attempt.

Thanks!
--Jacob

[1] https://postgr.es/m/CAOYmi%2BnCkoh3zB%2BGkZad44%3DFNskwUg6F1kmuxqQZzng7Zgj5tw%40mail.gmail.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-08-08 20:55:01 Re: Datum as struct
Previous Message Andres Freund 2025-08-08 20:30:58 Re: Datum as struct