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.

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