Skip to content

Conversation

@DimCitus
Copy link
Collaborator

@DimCitus DimCitus commented Sep 7, 2021

The step to reach the SINGLE state could be done from a pre-existing PGDATA,
such as taken from a backup tool. In that case, the postgresql.auto.conf
might have been installed with a setting that enables synchronous
replication.

Trouble is, we're initializing the first node in the system, and when we
reach the SINGLE state any setup for sync-rep does not make sense, we know
we don't have any secondary available.

Fixes #721

The step to reach the SINGLE state could be done from a pre-existing PGDATA,
such as taken from a backup tool. In that case, the postgresql.auto.conf
might have been installed with a setting that enables synchronous
replication.

Trouble is, we're initializing the first node in the system, and when we
reach the SINGLE state any setup for sync-rep does not make sense, we know
we don't have any secondary available.
@DimCitus DimCitus added bug Something isn't working good first issue Good for newcomers user experience Size: S Effort Estimate: Small labels Sep 7, 2021
@DimCitus DimCitus added this to the Sprint 2021 W35 W36 milestone Sep 7, 2021
@DimCitus DimCitus requested a review from JelteF September 7, 2021 14:07
@DimCitus DimCitus self-assigned this Sep 7, 2021
@DimCitus DimCitus merged commit c52ad9c into master Sep 7, 2021
@DimCitus DimCitus deleted the fix/empty-synchronous-standby-names-when-single branch September 7, 2021 14:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working good first issue Good for newcomers Size: S Effort Estimate: Small user experience

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Restoring a pg_basebackup coming from a cluster with primary and secondary into a single node should set synchronous_standby_names to ''

3 participants