Re: Big data INSERT optimization - ExclusiveLock on extension of the table - Mailing list pgsql-performance

From Jim Nasby
Subject Re: Big data INSERT optimization - ExclusiveLock on extension of the table
Date
Msg-id 0805fb3c-ed48-bece-690c-5e60c7b40e65@BlueTreble.com
Whole thread Raw
In response to Big data INSERT optimization - ExclusiveLock on extension of the table  (pinker <pinker@onet.eu>)
Responses Re: Big data INSERT optimization - ExclusiveLock on extension of the table  (pinker <pinker@onet.eu>)
List pgsql-performance
On 8/17/16 6:45 AM, pinker wrote:
> 1. rename table t01 to t02
OK...
> 2. insert into t02 1M rows in chunks for about 100k
Why not just insert into t01??
> 3. from t01 (previously loaded table) insert data through stored procedure
But you renamed t01 so it no longer exists???
> to b01 - this happens parallel in over a dozen sessions
b01?
> 4. truncate t01
Huh??
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)   mobile: 512-569-9461


pgsql-performance by date:

Previous
From: Jeff Janes
Date:
Subject: Re: Estimates on partial index
Next
From: Jim Nasby
Date:
Subject: Re: Estimates on partial index