Skip to content
This repository has been archived by the owner on Jan 21, 2021. It is now read-only.

Improve loading on partition tables #82

Open
cataphract opened this issue May 10, 2016 · 0 comments
Open

Improve loading on partition tables #82

cataphract opened this issue May 10, 2016 · 0 comments

Comments

@cataphract
Copy link
Contributor

Data should be loaded on tables without indexes or with the indexes disabled, in order to improve speed. The index should then be created at the end.

On PostgreSQL, this is fairly trivial, the parititioning tasklet has to be called twice, once before the main data load step to create the partition and another time afterwards to create the indexes (including primary keys and unique constraints).

On Oracle, the best way is to create a new unpartitioned table and then EXCHANGE this unpartitioned table for a new partition in the final table. The Oracle documentation has the details.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant