Re: Fix doc: explanation of how postgres works when OOM killer is invoked

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Takeshi Ideriha <iderihatakeshi(at)gmail(dot)com>
Cc: Manu <manuelreyesbravo(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Fix doc: explanation of how postgres works when OOM killer is invoked
Date: 2026-10-16 13:50:02
Message-ID: CAHGQGwGP1k+xw9y4nYi7se1RAC7m3JRxYpqD2PC=oSvNecOcxg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 15, 2026 at 5:27 PM Takeshi Ideriha
<iderihatakeshi(at)gmail(dot)com> wrote:
> On second thought, I agree with you. I'd like to keep the postgres doc
> concise as possible. Fixed in v3 patch.

I made a few minor adjustments and pushed the patch. Thanks!

Regards,

--
Fujii Masao

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ayush Tiwari 2026-10-16 13:58:13 Re: Add a pg_wal_preallocate() SQL function to eagerly create future WAL segments
Previous Message Fujii Masao 2026-10-16 13:47:28 Re: doc: fix pg_get_multixact_stats() num_mxids type (integer -> bigint)