Re: Lots of memory allocated when reassigning Large Objects

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Lots of memory allocated when reassigning Large Objects
Date: 2021-12-01 20:46:40
Message-ID: CAECtzeWD=0qGqgWG_8jLMby=as4JR==nnXfA47ARb2K_f-bLCg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Le mer. 1 déc. 2021 à 19:48, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> a écrit :

> Justin Pryzby <pryzby(at)telsasoft(dot)com> writes:
> > @Guillaume: Even if memory use with the patch isn't constant, I imagine
> it's
> > enough to have avoided OOM.
>
> I think it's good enough in HEAD. In the back branches, the sinval
> queue growth is bad enough that there's still an issue. Still,
> this is a useful improvement, so I added some comments and pushed it.
>
>
Thanks.

--
Guillaume.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2021-12-01 20:47:07 Re: Column Filtering in Logical Replication
Previous Message Alvaro Herrera 2021-12-01 20:29:47 Re: Column Filtering in Logical Replication