zalando / zalando/postgres-operator

Ways of migrating existing data

Open
#2,377 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
5.2k
Forks
1.1k
Avg merge
2d 16h
Merged PRs (30d)
3

Description

Please, answer some short questions which should help us to understand your problem / question better?

  • Which image of the operator are you using?: registry.opensource.zalan.do/acid/postgres-operator:v1.10.0
  • Where do you run it - cloud or metal? Kubernetes or OpenShift?: on premise vmWare Tanzu Cluster
  • Are you running Postgres Operator in production?: yes
  • Type of issue?: question

What are the best ways to migrate existing data into a new cluster? So far we connected to one cluster pod and used pg_dump/pg_restore from the original cluster.

I think, the s3-clone option is thought to be for clones that originate from a cluster also previously managed by the operator, right? (You can probably augment a basebackup from an existing cluster so it works for the s3-clone, but that's not the main focus)

Is there a way to put existing dump files somewhere that will be imported upon first startup or something?

Thanks.

Contributor guide

Open the contributing guide

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

Start with the operator's s3-clone configuration and the cluster first-startup/bootstrap flow, then compare those with the pg_dump/pg_restore and basebackup approaches mentioned here. Document which migration paths are supported for existing PostgreSQL data and whether dump files can be imported automatically; the issue is complete when the supported procedure and limitations are clear.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes, postgresql
Domain
databases, infrastructure
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.