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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
Cc: Mark Stosberg <mark(at)summersault(dot)com>, 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 17:54:20
Message-ID: 14665.1304531660@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> writes:
> On Wed, May 4, 2011 at 11:04 AM, Mark Stosberg <mark(at)summersault(dot)com> wrote:
>> 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.

The reason it works like that is that the SQL standard says so :-(
There was considerable angst about this when we made TRUNCATE recurse
to children, IIRC, but we decided we had to make it work that way.

regards, tom lane

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Kevin Grittner 2011-05-04 18:03:26 Re: Authentification via Kerberos with ProxyTicket
Previous Message Kevin Grittner 2011-05-04 17:46:30 Re: My server is oddly very slow