Re: Custom oauth validator options

From: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Nikolay Shaplov <dhyan(at)nataraj(dot)su>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, VASUKI M <vasukianand0119(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, myon(at)debian(dot)org
Subject: Re: Custom oauth validator options
Date: 2026-11-04 11:27:48
Message-ID: CAN4CZFOzZoe2NLVPWhqwgcf=rPdzJVRgMyGTfqusDs17P-Jaww@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 03 Nov 2026, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> I'm not crazy about this part though, I wonder if we should to put a hard cap
> with a ... or something? I'll see what I can come up with.

We could try that, but then we have to figure out a good maximum, and
that's difficult to do as there are only a few public validator
implementations.

What do you think about refactoring the function to use
ArrayBuildState instead, that would be a slightly bigger chance but
would result in cleaner code?

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hữu Đôn Hoàng 2026-11-04 11:49:38 Re: Print latency percentiles in pgbench
Previous Message Peter Eisentraut 2026-11-04 11:19:54 Re: pg_threads.h take II