Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: postgresql-cfbot/postgresql
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: cf/5781~1
Choose a base ref
...
head repository: postgresql-cfbot/postgresql
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: cf/5781
Choose a head ref
  • 3 commits
  • 14 files changed
  • 2 contributors

Commits on May 29, 2025

  1. Make GUC wal_receiver_timeout user-settable. 

    When multiple subscribers connect to different publisher servers,
it can be useful to set different wal_receiver_timeout values for
each connection to better detect failures. However, previously
this wasn't possible, which limited flexibility in managing subscriptions.

This commit changes wal_receiver_timeout to be user-settable,
allowing different values to be assigned using ALTER ROLE SET for
each subscription owner. This effectively enables per-subscription
configuration.
    @MasaoFujii
    MasaoFujii authored and Commitfest Bot committed May 29, 2025
    Configuration menu
    Copy the full SHA
    f92ece4 View commit details
    Browse the repository at this point in the history

  2. Add per-subscription wal_receiver_timeout setting. 

    This commit allows setting wal_receiver_timeout per subscription
using the CREATE SUBSCRIPTION and ALTER SUBSCRIPTION commands.
The value is stored in the subwalrcvtimeout column of the pg_subscription
catalog.

When set, this value overrides the global wal_receiver_timeout for
the subscription’s apply worker. The default is -1, which means the
global setting (from the server configuration, command line, role,
or database) remains in effect.

This feature is useful for configuring different timeout values for
each subscription, especially when connecting to multiple publisher
servers, to improve failure detection.

Bump catalog version.
    @MasaoFujii
    MasaoFujii authored and Commitfest Bot committed May 29, 2025
    Configuration menu
    Copy the full SHA
    24ad7e2 View commit details
    Browse the repository at this point in the history

  3. [CF 5781] v1 - Make wal_receiver_timeout configurable per subscription 

    This branch was automatically generated by a robot using patches from an
email thread registered at:

https://commitfest.postgresql.org/patch/5781

The branch will be overwritten each time a new patch version is posted to
the thread, and also periodically to check for bitrot caused by changes
on the master branch.

Patch(es): https://www.postgresql.org/message-id/5780e93c-7183-4aeb-b3a9-0a5ba0ff7e02@oss.nttdata.com
Author(s): Fujii Masao
    Commitfest Bot committed May 29, 2025
    Configuration menu
    Copy the full SHA
    9d9da8c View commit details
    Browse the repository at this point in the history
Loading