aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlvaro Herrera <alvherre@alvh.no-ip.org>2011-06-14 11:20:52 -0400
committerAlvaro Herrera <alvherre@alvh.no-ip.org>2011-06-14 11:27:25 -0400
commitfc7e99872cb3595638fc00ab96cf433bfa77fb14 (patch)
treed798abf523ec2ef386a8981ac4f4ba5b71366dc7
parentc3ad1e8dbd6cf1ff6d29bd2edb2da2c35187e768 (diff)
downloadpostgresql-fc7e99872cb3595638fc00ab96cf433bfa77fb14.tar.gz
postgresql-fc7e99872cb3595638fc00ab96cf433bfa77fb14.zip
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.
-rw-r--r--doc/src/sgml/ddl.sgml3
1 files changed, 2 insertions, 1 deletions
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>