| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Commitfest wrapup |
| Date: | 2022-04-09 17:14:44 |
| Message-ID: | CAM-w4HPMtzOfdpOuLH2d8O3mOHYcm7nyAjcgEcBQ=u1Pm-OxXQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, 9 Apr 2022 at 10:51, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> > Sound like bugfixes to be backpatched.
>
> Yeah. I'm not sure why these have received so little love.
Since bug fixes are important enough that they'll definitely get done
(and can happen after feature freeze) there's a bit of a perverse
incentive to focus on other things...
"Everybody was sure that Somebody would do it. Anybody could have done
it, but Nobody did it"
I think every project struggles with bugs that sit in bug tracking
systems indefinitely. The Open Issues is the biggest hammer we have.
Maybe we should be tracking "Open Issues" from earlier in the process
-- things that we think we shouldn't do a release without addressing.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2022-04-09 18:50:59 | Re: How about a psql backslash command to show GUCs? |
| Previous Message | Robert Haas | 2022-04-09 16:51:03 | Re: why pg_walfile_name() cannot be executed during recovery? |