Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • omnibus-gitlab omnibus-gitlab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 1,136
    • Issues 1,136
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 86
    • Merge requests 86
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • omnibus-gitlabomnibus-gitlab
  • Merge requests
  • !1416

Added support for Pg's hot_standby_feedback option

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged Yorick Peterse requested to merge hot-standby-feedback into master Mar 21, 2017
  • Overview 2
  • Commits 1
  • Pipelines 3
  • Changes 5

See https://www.postgresql.org/docs/9.6/static/runtime-config-replication.html#GUC-HOT-STANDBY-FEEDBACK for info about the option.

Enabling this cuts down the number of query conflicts on secondaries to 0:

postgres-stats__1_

Here the option was manually enabling a bit before 17:00. After enabling this I did not notice any change in table bloat. For the sake of safety the option is still disabled by default

@marin I added the CHANGELOG entry to 9.0.1. Is this something we're OK with releasing in a patch release, or do we want to wait for 9.1 (or somehow ninja it into 9.0)?

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: hot-standby-feedback