From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | jian he <jian(dot)universality(at)gmail(dot)com> |
Cc: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Antonin Houska <ah(at)cybertec(dot)at>, Peter Eisentraut <peter(at)eisentraut(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PoC] Federated Authn/z with OAUTHBEARER |
Date: | 2024-11-04 09:11:35 |
Message-ID: | 2C38E99A-9DD9-4E19-894E-C0905505074C@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On 4 Nov 2024, at 06:00, jian he <jian(dot)universality(at)gmail(dot)com> wrote:
> + if (cnt != 1)
> + {
> + /*
> + * Either the lexer screwed up or our assumption above isn't true, and
> + * either way a developer needs to take a look.
> + */
> + Assert(cnt == 1);
> + return 1; /* don't fall through in release builds */
> + }
> The above Assert looks very wrong to me.
I think the point is to fail hard in development builds to ensure whatever
caused the disconnect between the json lexer and sscanf parsing is looked at.
It should probably be changed to Assert(false); which is the common pattern for
erroring out like this.
--
Daniel Gustafsson
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2024-11-04 09:24:09 | Re: proposal: schema variables |
Previous Message | Bertrand Drouvot | 2024-11-04 08:52:04 | Re: Clear padding in PgStat_HashKey keys |