On 9/18/25 2:19 PM, Nathan Bossart wrote:
On Thu, Sep 18, 2025 at 01:38:44PM -0400, Robert Haas wrote:That seems completely backwards to me. We should go with the version that was submitted weeks ago and upon which people have had the opportunity to comment unless you can justify each change that you now want to make at the last minute. Why for example should we drop mentioning the ability to return OLD.* and NEW.* in favor of mentioned UUIDv7? I'd argue that the former is more important than the latter, and I don't see how you can argue otherwise except by appealing to the research you've done over the last several weeks. But none of us have access to that or got a vote in it. These things ought to be decided by consensus. If you want your research to feed into the building of that consensus, you need to do it and present it earlier. For example, if you want to present survey results, I think that's a great way to help decide these kinds of things, but then other people should have the right to present their own survey results and so on in that conversation too.Quick analysis of the differences: Common: * AIO * skip scan * pg_upgrade * UUIDv7 * virtual generated columns * OAuth Only v1 (my patch): * OLD/NEW for RETURNING * temporal constraints * EXPLAIN enhancements Only v2 (Jonathan's): * conflict logging While the EXPLAIN enhancements and conflict logging items seem like super useful features, I can see how there might be disagreement over whether they belong in the major features list. I'm a little more surprised about the omission of OLD/NEW and temporal contraints in v2, though. That being said, I'm tempted to suggest we UNION the two lists, bikeshed over the exact wording for a few hours, and then call it day...
Let's hack on this together for a few and bring a proposal to the list. Jonathan
OpenPGP_signature.asc
Description: OpenPGP digital signature
