postgrespro.git / summary / log / commit / refs

commit    e1218f59ea4c0605e72298fa121d5aef4c66def2
Author:   Alvaro Herrera <alvherre@alvh.no-ip.org>
Date:     Wed May 20 18:35:39 2020 +0000

    doc: Adding a partition does not require Access Exclusive lock
    
    This doc update was missed in 898e5e3290a7.  Backpatch to 12.
    
    Pointed out by Pavel Luzanov
    Discussion: https://postgr.es/m/642e9fbc-b832-698b-9a8f-d626afd7014d@postgrespro.ru


 doc/src/sgml/ddl.sgml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
index d4c5ce8d8a..991323d347 100644
--- a/doc/src/sgml/ddl.sgml
+++ b/doc/src/sgml/ddl.sgml
@@ -4121,8 +4121,8 @@ ALTER INDEX measurement_city_id_logdate_key
       <listitem>
        <para>
         Some operations require a stronger lock when using declarative
-        partitioning than when using table inheritance.  For example, adding
-        or removing a partition to or from a partitioned table requires taking
+        partitioning than when using table inheritance.  For example,
+        removing a partition from a partitioned table requires taking
         an <literal>ACCESS EXCLUSIVE</literal> lock on the parent table,
         whereas a <literal>SHARE UPDATE EXCLUSIVE</literal> lock is enough
         in the case of regular inheritance.


[parent: 39cb2ee09cf9]