pg.ddx.io  GitHub: pgjdbc/pgjdbc (issues + PRs as email threads)  
help / color / mirror / Atom feed
From: vlsi (@vlsi) <noreply+vlsi@github.com>
To: pgjdbc/pgjdbc <noreply+pgjdbc-pgjdbc@github.com>
Subject: Re: [pgjdbc/pgjdbc] PR #4251: OAuth implementation
Date: Fri, 23 Oct 2026 06:03:06 +0000
Message-ID: <gh-pgjdbc-pgjdbc-4251-c6358571869@github.com> (raw)
In-Reply-To: <gh-pgjdbc-pgjdbc-4251@github.com>
References: <gh-pgjdbc-pgjdbc-4251@github.com>

> Everything else in vlsi's review can be a follow-up issue.

Dave, OAuth relates to security, and merging code that violates RFCs and so on can easily result in CVEs.

>That is why I'm fixing the list here instead of asking for another round.

As you might know, PostgreSQL team decided to postpone PostgreSQL release after LLMs surfaced issues in human-merged changes.

LLM finding new stuff does not mean it will always new stuff. It will converge as defects get fixed.

If you do not want fixing the issues, I can help with that.

view thread (168+ messages)  latest in thread

Message-ID: <gh-pgjdbc-pgjdbc-4251-c6358571869@github.com>
Permalink:  ../gh-pgjdbc-pgjdbc-4251-c6358571869@github.com/

 · 


This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox