From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
---|---|
To: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | ITYM DROP TABLE |
Date: | 2011-06-13 21:44:05 |
Message-ID: | 79A3A7F7-4448-4927-A1ED-104EF2B360D8@kineticode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I was reading the partitioning docs when I spotted this. I think it means to highlight the advantages of DROP TABLE over DELETE rather than ALTER TABLE.
Best,
David
diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
index 4c9fc5d..0cdb800 100644
*** a/doc/src/sgml/ddl.sgml
--- b/doc/src/sgml/ddl.sgml
*************** VALUES ('New York', NULL, NULL, 'NY');
*** 2332,2338 ****
<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.
It also entirely avoids the <command>VACUUM</command>
overhead caused by a bulk <command>DELETE</>.
</para>
--- 2332,2338 ----
<para>
Bulk loads and deletes can be accomplished by adding or removing
partitions, if that requirement is planned into the partitioning design.
! <command>DROP TABLE</> is far faster than a bulk operation.
It also entirely avoids the <command>VACUUM</command>
overhead caused by a bulk <command>DELETE</>.
</para>
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2011-06-13 22:00:02 | Re: wrong message on REASSIGN OWNED |
Previous Message | Dan Ports | 2011-06-13 20:29:05 | Re: SSI patch renumbered existing 2PC resource managers?? |