From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ITYM DROP TABLE |
Date: | 2011-06-14 18:39:15 |
Message-ID: | BANLkTikWHyMzDLiWJRamq-kZqjoYhzDXxQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jun 13, 2011 at 10:44 PM, David E. Wheeler <david(at)kineticode(dot)com> wrote:
> 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>
That looks weird. I'm sure that *used* to say DROP TABLE.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2011-06-14 18:43:33 | Re: SSI patch renumbered existing 2PC resource managers?? |
Previous Message | Bruce Momjian | 2011-06-14 18:38:14 | Re: One-Shot Plans |