darold / darold/ora2pg

Load data of one partitioned table in several threads

Open
#720 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Perl
Stars
1.2k
Forks
378
PR merge metrics
No merged PRs in 30d

Description

When i'm load data from one oracle partitioned table into postgres, the ora2pg (last version) execute transfer consequently for every partition of this table (i see it in session browser), for example:

SELECT "INFO_ID", ...
  FROM BSO_TEST2.KBLN_INFO SUBPARTITION (sys_subp11915) a
[>                        ]       0/1318381 rows (0.0%) Table SYS_SUBP11915 (1 sec., 0 recs/sec)
[>                        ]       0/1318381 rows (0.0%) Table SYS_SUBP11916 (0 sec., 0 recs/sec)
[>                        ]   45405/1318381 rows (3.4%) Table SYS_SUBP11917 (5 sec., 9081 recs/sec)
[>                        ]       0/1318381 rows (0.0%) Table SYS_SUBP11744 (0 sec., 0 recs/sec)
[>                        ]       0/1318381 rows (0.0%) Table SYS_SUBP11745 (0 sec., 0 recs/sec)
[>                        ]       4/1318381 rows (0.0%) Table SYS_SUBP11746 (0 sec., 4 recs/sec)
[>                        ]    1179/1318381 rows (0.1%) Table SYS_SUBP11747 (0 sec., 1179 recs/sec)

Is it posible to run it in parallel threads?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files, tests, or entry points are named in the issue. Start by locating the code that iterates over Oracle partitions and subpartitions during data transfer; done means those partitions can be transferred concurrently without changing migration results.

Written by the indexing model from the issue text.

Assessment

Tech stack
perl, postgresql
Domain
databases
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.