Re: Large objects and out-of-memory

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Large objects and out-of-memory
Date: 2020-12-28 13:22:42
Message-ID: X+ncIgEQ67aV/2oj@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Dec 25, 2020 at 10:51:00AM +0900, Michael Paquier wrote:
> Good catch. It is very easy to miss that this is not "rm", but "sn".
> I have checked the rest of this area and did not notice similar
> errors. I'll backpatch the attached if there are no objections.

Applied this one with 643428c & co.
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2020-12-28 15:14:10 Re: BUG #16793: Libxml2 contains a null pointer dereference flaw in xpath.c
Previous Message PG Bug reporting form 2020-12-28 12:49:43 BUG #16794: BEFORE UPDATE FOR EACH ROW triggers on partitioned tables can break tuple moving UPDATEs