| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> |
| Cc: | PostgreSQL Hackers <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-05 20:37:04 |
| Message-ID: | EBC64452-C2B4-4768-93B4-E1FE6D07726E@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 4 Nov 2026, at 12:27, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> wrote:
>
> 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?
After thinking about this some more I think going this route is the better
option, even if that means that it will be deferred to v20 at this point. I
agree that it would be nice to have the options in the view in 19, but it's not
a showstopper. We are very close to release and I don't want us to rush
something in which we might want to backtrack on already in 20.
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Smith | 2026-11-05 20:45:08 | Re: BUG? Unpublished generated columns are reported "missing" by the subscription |
| Previous Message | Nathan Bossart | 2026-11-05 20:31:07 | Re: Teach pg_upgrade to deal with invalid databases |