From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Release 14 Schedule |
Date: | 2021-09-25 15:40:39 |
Message-ID: | 2515096.1632584439@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Still, this kind of seems like a laundry list to me. I'd argue for
> cutting range types, extended statistics, SEARCH / CYCLE, TOAST, and
> emergency mode vacuum. They're all nice, and I'm glad we have them,
> but they're also things that only people who are deeply steeped in
> PostgreSQL already seem likely to appreciate. Better scalability, less
> bloat, working OUT parameters, and query pipelining have benefits
> anyone can understand.
But of course it's a laundry list, and it's aimed at people steeped
in Postgres, because who else is going to be reading release notes?
Anyway, after re-reading the list, I concur that the TOAST item
shouldn't make the cut, so I took that out along with the explicit
mention of FDWs, and added something about emergency vacuum.
Pushed at
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=765f677f364100072160e7af37288eb1df2ff355
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-09-25 15:43:16 | Re: Fixing WAL instability in various TAP tests |
Previous Message | Mark Dilger | 2021-09-25 15:20:06 | Re: Fixing WAL instability in various TAP tests |