postgres.git / summary / log / commit / refs

commit    d60ce59963cab7fa142464c90a3e9d2ab5496640
Author:   Alvaro Herrera <alvherre@alvh.no-ip.org>
Date:     Tue Jun 14 15:20:52 2011 +0000
First released in: 9.2.0, 9.0.5, 9.1.0

    Mention DROP TABLE as well as ALTER TABLE NO INHERIT
    
    ... when talking about how good they are in replacement of bulk DELETE
    in partitioned setups.
    
    The original wording was a bit confusing.
    
    Per an observation from David Wheeler.


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

diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
index 4c9fc5d57a1..c250faec4ee 100644
--- a/doc/src/sgml/ddl.sgml
+++ b/doc/src/sgml/ddl.sgml
@@ -2332,7 +2332,8 @@ VALUES ('New York', NULL, NULL, 'NY');
      <para>
       Bulk loads and deletes can be accomplished by adding or removing
       partitions, if that requirement is planned into the partitioning design.
-      <command>ALTER TABLE</> is far faster than a bulk operation.
+      <command>ALTER TABLE NO INHERIT</> and <command>DROP TABLE</> are
+      both far faster than a bulk operation.
       It also entirely avoids the <command>VACUUM</command>
       overhead caused by a bulk <command>DELETE</>.
      </para>


[parent: 6fdd89750342]