Postgres db Update to Version 15

From: "Ritthaler, Axel" <axel(dot)ritthaler(at)sap(dot)com>
To: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Cc: "Hambrecht, Felix" <felix(dot)hambrecht(at)sap(dot)com>
Subject: Postgres db Update to Version 15
Date: 2023-12-09 12:26:53
Message-ID: PAVPR02MB97956F7C5E02F8CFE19DE7A08089A@PAVPR02MB9795.eurprd02.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dear Postgres Team,

We are contacting you today to get your feedback on a service degradation, that occurred, after upgrading related postgres databases to db-Version 15.

We upgraded several Live- and Non-Live-Landscapes to db-Version 15, coming from db-version 11. One AWS-Live-Landscape showed an increasing CPU-Usage from 5 % to 100% with the effect, that Lifecycle Operations on customer side were experiencing intermittent availability issues several times and with a max period of 186 minutes of degradation.

The Root Cause of this behavior, as aligned with AWS RDS Support, has been a new feature-set coding (parallel_feature_query) with Postgres Version 15, that shows a different behavior due to related parameter (max_parallel_workers_per_gather).
This parameter sets the maximum number of workers, that can be started by a single Gather or Gather Merge node. Parallel workers are taken from the pool of processes established by max_worker_processes, limited by max_parallel_workers. The default value is 2. Setting this value to 0 disabled parallel query execution and resolved the issue.

Remaining question now is, what has to be done to move related Live-Landscapes back to the default parameter value (2) without creating the same impact again.

Did you see such behavior with other customers ?
What is your suggestion and recommended way-forward to enable parallel-worker setup again ?

Thanks and kind regards

Axel Ritthaler

BTP Development Manager, BTP FP CF WDF

SAP SE Dietmar-Hopp-Allee 16, 69190 Walldorf, Germany

E: axel(dot)ritthaler(at)sap(dot)com<mailto:axel(dot)ritthaler(at)sap(dot)com>

M: +4915153858987<tel:%20+4915153858987> T: +496227774698<tel:%20+496227774698>

Please consider the impact on the environment before printing this e-mail.

[cid:image001(dot)png(at)01DA2AA3(dot)3D7C67D0]

Pflichtangaben/Mandatory Disclosure Statement: www.sap.com/impressum

Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank.

This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2023-12-09 12:31:32 Re: Why are wal_keep_size, max_slot_wal_keep_size requiring server restart?
Previous Message Hannu Krosing 2023-12-09 11:56:23 Re: Emitting JSON to file using COPY TO