From 8f4edadb09355c805f4bad6179170db1e15b2235 Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Sun, 24 Oct 2004 22:43:56 +0000
Subject: [PATCH] Add note that REINDEX takes a weaker lock than it used to.
---
doc/src/sgml/release.sgml | 14 +++++++++++++-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml
index 0ca053c27d5..466754b11ff 100644
--- a/doc/src/sgml/release.sgml
+++ b/doc/src/sgml/release.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.302 2004/10/22 00:25:18 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.303 2004/10/24 22:43:56 tgl Exp $
-->
<appendix id="release">
@@ -1170,6 +1170,18 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.302 2004/10/22 00:25:18 tgl Exp
</para>
</listitem>
+ <listitem>
+ <para>
+ <command>REINDEX</command> does not exclusively lock the index's
+ parent table anymore
+ </para>
+ <para>
+ The index itself is still exclusively locked, but readers of the
+ table can continue if they are not using the particular index
+ being rebuilt.
+ </para>
+ </listitem>
+
<listitem>
<para>
Erase MD5 user passwords when a user is renamed (Bruce)
--
GitLab