DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	b=BALNXBFPS9OG5jasdVRP5NS74pVrciGDfh3LUXtkFwy5Kmb0GOzTS8rt7+Zyt9EyRh
	4zivY8NRBvpDeTryyUEDrEp74xZDnvf1hhKEHUhqVXPSswDgcqgTJ3qeLEXIXcXrAcRn
	nWacneAlgNL6HgMmkMeer261Nh5NZnO9pkm2k=
MIME-Version: 1.0
In-Reply-To: <ips0v8$8ut$1@dough.gmane.org>
References: <ip9abr$nk8$1@dough.gmane.org>
	<659395.83416.qm@web39708.mail.mud.yahoo.com>
	<ips01d$351$1@dough.gmane.org>
	<BANLkTinRFTF0ywHQua9ZgJ28sEqdKxNHXA@mail.gmail.com>
	<ips0v8$8ut$1@dough.gmane.org>
Date: Wed, 4 May 2011 11:33:03 -0600
Message-ID: <BANLkTinieDbJ5dabJDX7v_JzTGSkKxpsMA@mail.gmail.com>
Subject: Re: Re: best practice for moving millions of rows to child
	table when setting up partitioning?
From: Scott Marlowe <scott.marlowe@gmail.com>
To: Mark Stosberg <mark@summersault.com>
Cc: pgsql-admin@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1

On Wed, May 4, 2011 at 11:04 AM, Mark Stosberg <mark@summersault.com> wrote:
> It is not as findable as it could be then. Besides scanning the page, I
> also searched for "child", "parent" and "partition", and none of those
> words are mentioned. Neither is "inherit". Pulling out "ONLY" to have
> it's own "Parameter" sub-heading also help, instead of bundling that
> documentation under the "name" sub-heading.
>
> I suggest that at least one of the above search terms be added to better
> relate the documentation to the partitioning documentation.

Agreed.

> Further, since TRUNCATE permanently and instantly deletes mass amounts
> of data, I would hope that it would provide "safety" by default, but
> only truncating one table unless I specify otherwise.

Keep in mind you're using postgres, the only thing you can't wrap in a
transaction is create / drop tablespace or database.  So you can test
your truncate within a transaction to be sure it's doing what you
want.