Re: pgsql: Make GetSnapshotData() more resilient on out-of-memory errors

From: Aleksander Alekseev <aleksander(at)tigerdata(dot)com>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Cc: Michael Paquier <michael(at)paquier(dot)xyz>
Subject: Re: pgsql: Make GetSnapshotData() more resilient on out-of-memory errors
Date: 2026-11-09 08:26:50
Message-ID: CAJ7c6TO+7rrN5H_Odd8PLdmrEa4MgeoJ2AqnTydOcy=AyZvDsQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Hi Michael,

> This problem is unlikely going to show up in practice, so no backpatch.

A customer reported offlist that the issue is reproducible in practice
on PostgreSQL 18. I suggest backpatching this.

--
Best regards,
Aleksander Alekseev

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2026-11-09 09:27:25 pgsql: psql: Stop scripts on Ctrl+C while waiting for COPY or prompt in
Previous Message Michael Paquier 2026-11-09 08:05:21 pgsql: pgstattuple: Reject unlogged and temporary relations during reco

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2026-11-09 08:42:01 Re: extension_control_path: ignore empty elements and deduplicate directories
Previous Message Michael Paquier 2026-11-09 08:10:23 Re: Reject access to unlogged tables in contrib modules