From: Scott Marlowe <scott.marlowe@gmail.com>
To: Mark Stosberg <mark@summersault.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Re: best practice for moving millions of rows to child table when setting up partitioning?
Date: Wed, 4 May 2011 11:33:03 -0600
Message-ID: <BANLkTinieDbJ5dabJDX7v_JzTGSkKxpsMA@mail.gmail.com> (raw)
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>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott.marlowe@gmail.com, mark@summersault.com
Subject: Re: Re: best practice for moving millions of rows to child table when setting up partitioning?
In-Reply-To: <BANLkTinieDbJ5dabJDX7v_JzTGSkKxpsMA@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox