On Mon, Apr 25, 2011 at 10:53 AM, Raghavendra
<raghavendra.rao@enterprisedb.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.
