Re: Unexpected behavior after OOM errors

From: Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Alexander Lakhin <exclusion(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Unexpected behavior after OOM errors
Date: 2026-07-21 09:41:58
Message-ID: CAEze2Wh0+MQkfXLjW6Sa8ntYqg8ttjjjqTgsyBVYAssyJA3p1w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 21 Jul 2026 at 09:55, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Tue, Jul 21, 2026 at 07:41:23AM +0900, Michael Paquier wrote:
> > Neater to not call AllocSetContextCreate() in the cache context this
> > way, indeed. That's better than what I have sent.
>
> Applied this one. I have not looked more at the three others.

Thanks! Sorry for the conflicting patches, I'd missed the mail with yours.

Kind regards,

Matthias

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hayato Kuroda (Fujitsu) 2026-07-21 09:45:20 RE: Validate SERVER subscription conninfo during ALTER SUBSCRIPTION ... OWNER TO
Previous Message Jonathan Gonzalez V. 2026-07-21 09:39:41 Re: log_min_messages per backend type