turicas/rows

pgimport enhancements

Open

#353 opened on Jul 19, 2020

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Python (136 forks)github user discovery
enhancementhelp wantedplugin

Repository metrics

Stars
 (886 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

  • It's very useful to run VACUUM ANALYZE tablename; just after importing data, so we could have an option on pgimport to do it (function and CLI).
  • The performance of pgimport could be better if vacuum for the imported table is disabled before import (ALTER TABLE tablename SET (autovacuum_enabled = off);) and then (after import) re-enabled. This could be the default behaviour but may be an option to disable it (could be useful in cases where we're importing data into an existing table).

Contributor guide

Research direction
Review the pgimport function and CLI, then implement a parameter to run VACUUM ANALYZE after import. Optionally, add logic to disable and re enable autovacuum on the table before and after import for better performance.
Tech stack
pythonpostgresql
Domain
backenddatabase
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Python
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70