Re: Re: best practice for moving millions of rows to child table when setting up partitioning?

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Mark Stosberg <mark(at)summersault(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Re: best practice for moving millions of rows to child table when setting up partitioning?
Date: 2011-05-04 16:54:33
Message-ID: BANLkTinRFTF0ywHQua9ZgJ28sEqdKxNHXA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Wed, May 4, 2011 at 10:48 AM, Mark Stosberg <mark(at)summersault(dot)com> wrote:
>
>>> 5. Finally, I'll drop the indexes on the parent table and
>>> truncate it.
>
> Luckily I noticed the problem with TRUNCATE and partitioning before my
> work got to production.
>
> TRUNCATE cascades automatically and silently to child tables, which was
> not my intent.
>
> This is mentioned here:
> http://wiki.postgresql.org/wiki/Table_partitioning
>
> But is not mentioned in the official documentation for TRUNCATE:
>
> http://www.postgresql.org/docs/9.0/static/sql-truncate.html

Surely it is. Quoting:

"If ONLY is specified, only that table is truncated. If ONLY is not
specified, the table and all its descendant tables (if any) are
truncated. "

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Mark Stosberg 2011-05-04 17:04:39 Re: Re: best practice for moving millions of rows to child table when setting up partitioning?
Previous Message Mark Stosberg 2011-05-04 16:48:44 Re: best practice for moving millions of rows to child table when setting up partitioning?