Re: Partitioning an existing table

From: Vick Khera <vivek(at)khera(dot)org>
To: PG-General Mailing List <pgsql-general(at)postgresql(dot)org>
Subject: Re: Partitioning an existing table
Date: 2011-04-25 15:16:08
Message-ID: BANLkTi=h1DG9XCCreO_3pCjACjW4zVpCXQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Apr 25, 2011 at 10:53 AM, Raghavendra <
raghavendra(dot)rao(at)enterprisedb(dot)com> wrote:

> 1. Send all the data to .csv file with COPY TO command of the base
> table(which will undergo for partition).
> 2. Create the partition setup with TRIGGER's
> 3. Use COPY FROM command for inserting data into partition table.
>

so now when your running application goes to query the table, it gets
doubles? if you do it in transactions, then how long are you going to cause
the master table to be locked when doing such a bulk delete?

my point is to minimize service interruption, and that means moving small
hunks at a time to minimize the locks needed.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Phoenix Kiula 2011-04-25 16:16:17 Re: Help - corruption issue?
Previous Message David Johnston 2011-04-25 15:13:48 Re: 10 missing features