| From: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Melanie Plageman <melanieplageman(at)gmail(dot)com>, Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: scary patch contest |
| Date: | 2026-08-26 18:07:00 |
| Message-ID: | CALj2ACWLfDxsGdFVG-dbqUttyS11mrmpRMY+NrrbjTgeXB9oqA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Wed, Aug 26, 2026 at 8:54 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> It's not exactly a
> coincidence that all of the features that have had all of these fixups
> were committed quite close to feature freeze. If they'd been committed
> on, say, August 26th of last year, there's a good chance that they
> would have had most of the bugs flushed out by now.
+1. IMHO, trying to get complex features whose design has consensus
early in the development cycle is the best way to give enough time for
such features to settle. However, this may not always be possible,
because getting consensus itself takes time, and so does review.
Others may have different thoughts on this.
--
Bharath Rupireddy
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florin Irion | 2026-08-26 18:07:07 | Re: Proposal: Supporting URI SAN in Certificate Authentication |
| Previous Message | Jingtang Zhang | 2026-08-26 17:27:20 | Re: Allow aggressive VACUUM to freeze without a cleanup lock |