Project

General

Profile

Actions

Bug #22281

closed

Remove checkpoint_segments from database optimsation doc

Added by Vincent MEMBRÉ about 1 year ago. Updated about 1 year ago.

Status:
Released
Priority:
N/A
Category:
Documentation
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No

Description

This parameter was deprecated in Postgres 9.5 and was removed in latest released of postgres (at least 12).

It is replaced by another parameter (max_wal_size) but the default value is reaaly higher than what we used to set

so we should probably remove it fromour config until we have time to analyse at which point it has an impact on performance

Actions #1

Updated by Vincent MEMBRÉ about 1 year ago

  • Status changed from New to In progress
  • Assignee set to Vincent MEMBRÉ
Actions #2

Updated by Vincent MEMBRÉ about 1 year ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder-doc/pull/945
Actions #3

Updated by Vincent MEMBRÉ about 1 year ago

  • Subject changed from Remove checkpoint_segment from database optimsation doc to Remove checkpoint_segments from database optimsation doc
Actions #4

Updated by Vincent MEMBRÉ about 1 year ago

  • Status changed from Pending technical review to Pending release
Actions #5

Updated by Alexis Mousset about 1 year ago

  • Fix check changed from To do to Checked
Actions #6

Updated by Vincent MEMBRÉ about 1 year ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 7.2.4 which was released today.

Actions

Also available in: Atom PDF