diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2011-06-14 11:20:52 -0400 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2011-06-14 11:20:52 -0400 |
| commit | 247fd8105aa6bcb3201dbc19e206fcb27b940040 (patch) | |
| tree | f85f0f6d7225b604d788876118fb8087fa35bd35 | |
| parent | a03f1d399dbfdc87798742329270d99962216100 (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 86cf6ec8fc4..caa986f18d7 100644 --- a/doc/src/sgml/ddl.sgml +++ b/doc/src/sgml/ddl.sgml @@ -2320,7 +2320,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> |