diff options
| author | Alvaro Herrera | 2011-06-14 15:20:52 +0000 |
|---|---|---|
| committer | Alvaro Herrera | 2011-06-14 16:42:02 +0000 |
| commit | d60ce59963cab7fa142464c90a3e9d2ab5496640 (patch) | |
| tree | b01731d538a1158bcf948bdf7f2183a6bdcfd47d | |
| parent | 6fdd8975034249f7c1a97bfb4991e6bde250c6ea (diff) | |
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.sgml | 3 |
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> |