Re: Proposal: GUC to control starting/stopping logical subscription workers

From: SATYANARAYANA NARLAPURAM <satyanarlapuram(at)gmail(dot)com>
To: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Proposal: GUC to control starting/stopping logical subscription workers
Date: 2025-09-09 20:16:12
Message-ID: CAHg+QDc4buCLnGheeXYsjFEc3UnCBe=momKQdt_xpJF-PCXqgQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

HI Bharat,

>
> If I understand correctly, the end effect is similar to disabling all
> subscriptions. Why not just add ALTER SUBSCRIPTION ... DISABLE for all
> subscriptions in the failover work flow? Migration of logical
> replication slots docs says so -
> https://www.postgresql.org/docs/18/logical-replication-upgrade.html.
>

The scenarios I am talking in this case are no major version upgrade, but
PITR and Standby promotion cases.
Server is in read only mode (catalog cannot be updated) before promotion
and subscriptions cannot be disabled.

> --
> Bharath Rupireddy
> PostgreSQL Contributors Team
> RDS Open Source Databases
> Amazon Web Services: https://aws.amazon.com
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Melanie Plageman 2025-09-09 20:29:44 Re: Incorrect logic in XLogNeedsFlush()
Previous Message Masahiko Sawada 2025-09-09 20:15:43 Re: Make COPY format extendable: Extract COPY TO format implementations