ClusterLabs / ClusterLabs/PAF

Sync replication and replication slot problem

Open
#41 5 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Perl
Stars
350
Forks
55
PR merge metrics
No merged PRs in 30d

Description

Hello,

For one of our customer we have to use sync with `synchronous_standby_names = '*'` in postgresql.conf combine with replication slot in database.

There is a problem when one standby leave the cluster, replication slot stays in DB and PGSQL keeps its wal, due to the synchronous_standby_names in config, untill the standby come back. If the stanbdy is not present for a long time, wal directory will grow untill partition is full...

So do you think it'll be possible to manage replication slot with PAF RA ?

Regards,
Pascal.

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no files or tests; start by reviewing PAF's PostgreSQL resource-agent handling alongside PostgreSQL replication slots and synchronous_standby_names. Define how a departed standby's slot should be managed, then verify that WAL retention is controlled without disrupting failover.

Written by the indexing model from the issue text.

Assessment

Tech stack
perl, postgresql
Domain
databases, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.