On Wed, Jun 23, 2021 at 07:45:53AM -0700, Peter Geoghegan wrote:
> On Wed, Jun 23, 2021 at 5:50 AM Simon Riggs
> <simon.ri...@enterprisedb.com> wrote:
> > I just noticed that these commits are missing, yet are very important
> > new features:
> > d9d076222f5b94a8
> > f9900df5f9
> > c98763bf51bf
> >
> > These are important enough to be major features of PG14.
>
> I certainly think that they're important enough to be mentioned.
OK, here is a doc patch to add a mention of this. I originally thought
this was an optimization that wouldn't be of general interest.
--
Bruce Momjian <br...@momjian.us> https://momjian.us
EDB https://enterprisedb.com
If only the physical world exists, free will is an illusion.
diff --git a/doc/src/sgml/release-14.sgml b/doc/src/sgml/release-14.sgml
index 33b7bf7d57..b6c6a9826f 100644
--- a/doc/src/sgml/release-14.sgml
+++ b/doc/src/sgml/release-14.sgml
@@ -740,6 +740,28 @@ Author: Peter Geoghegan <p...@bowt.ie>
<listitem>
<!--
+Author: Alvaro Herrera <alvhe...@alvh.no-ip.org>
+2020-11-25 [c98763bf5] Avoid spurious waits in concurrent indexing
+Author: Alvaro Herrera <alvhe...@alvh.no-ip.org>
+2021-01-15 [f9900df5f] Avoid spurious wait in concurrent reindex
+Author: Alvaro Herrera <alvhe...@alvh.no-ip.org>
+2021-02-23 [d9d076222] VACUUM: ignore indexing operations with CONCURRENTLY
+-->
+
+ <para>
+ Allow vacuum to be more aggressive in removing expired rows during
+ certain index operations (Álvaro Herrera)
+ </para>
+
+ <para>
+ Specifically, <command>CREATE INDEX CONCURRENTLY</command> and
+ <command>REINDEX CONCURRENTLY</command> no longer limit row
+ expiration of other relations.
+ </para>
+ </listitem>
+
+ <listitem>
+<!--
Author: Fujii Masao <fu...@postgresql.org>
2020-12-08 [e2ac3fed3] Speed up rechecking if relation needs to be vacuumed or
-->
