restore and pg_control #313

Open

Open

restore and pg_control#313

Labels

Contributor

To prevent instance from starting in the middle of restore:

When running regular restore, we must copy pg_control at the very end.
When running incremental restore, we must drop pg_control first.

added

added this to the 2.5.0 milestone

ContributorAuthor

INFO: Running incremental restore into nonempty directory: "/data/postgresql"
INFO: Trying to read pg_control file in destination direstory
ERROR: Could not open file "/data/postgresql/global/pg_control" for reading: No such file or directory

added a commit that references this issue

on Jun 16, 2021

[Issue #313] restore pg_control last

linked a pull request that will close this issue[Issue #313] restore pg_control last #399

on Jun 16, 2021

added 3 commits that reference this issue

on Jun 16, 2021

[Issue #313] review feedback

[Issue #313] added test coverage

[Issue #313] improve test coverage

added a commit that references this issue

on Jun 18, 2021

[Issue #313] add test incr_restore.IncrRestoreTest.test_incr_restore_…

modified the milestones: 2.5.2, 2.5.3

on Oct 15, 2021

modified the milestones: 2.5.4, 2.5.5

on Dec 22, 2021

modified the milestones: 2.5.5, 2.5.6

on Feb 16, 2022

modified the milestones: 2.5.6, 2.5.7

on May 26, 2022

removed this from the 2.5.7 milestone

on Sep 14, 2022

to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

[Issue #313] restore pg_control lastpostgrespro/pg_probackup

Participants