| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Intention to start an [oauth] "working group" |
| Date: | 2025-11-04 18:23:16 |
| Message-ID: | CAOYmi+k_FC1+S9i+yfLXvo2rpvJQC_EYjtZ3c4ZSa909t7WFtg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Nov 3, 2025 at 8:35 AM Melanie Plageman
<melanieplageman(at)gmail(dot)com> wrote:
> All of those ideas make sense.
Thanks! I've added the tag; let's see how this goes.
> I haven't followed oauth development enough to know if all related
> threads and CF entries are more obviously related, but it seems like a
> good idea for big multi-release projects to bucket their work somehow
> for ease of consumption of those less in the weeds.
There is some overlap with other authentication subprojects, but
probably not as much as AIO is dealing with, which makes things a
little easier. I imagine this will need some refinement at some point
(if it works).
--Jacob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-11-04 18:31:32 | Re: Fix ALTER TABLE DROP EXPRESSION with inheritance hierarchy |
| Previous Message | Tom Lane | 2025-11-04 18:16:05 | Re: Fix ALTER TABLE DROP EXPRESSION with inheritance hierarchy |