Re: oauth integer overflow

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Jacob Champion <champion(dot)p(at)gmail(dot)com>
Subject: Re: oauth integer overflow
Date: 2026-04-23 17:49:42
Message-ID: CAOYmi+n4U_g+k1Bfs2eavJdps0qQj3HFDa5i3V1c0m3CLYUWhA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Apr 23, 2026 at 10:29 AM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> > On 23 Apr 2026, at 18:12, Andres Freund <andres(at)anarazel(dot)de> wrote:
> > I think this should use pg_add_s32_overflow().

Agreed, thanks for the report!

> Agreed, I'll write up a patch to fix it.

Cool. I have one written up and can share it for comparison, if you'd
like, but it's fairly verbose and I wonder if there's a better way to
do it.

--Jacob

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Dilger 2026-04-23 17:57:28 Re: GUC parameter ACLs and physical walsender
Previous Message Daniel Gustafsson 2026-04-23 17:28:43 Re: oauth integer overflow