Horton

Re: Lots of memory allocated when reassigning Large Objects

Guillaume Lelarge <guillaume@lelarge.info>

View thread View on postgr.es
From: Guillaume Lelarge <guillaume@lelarge.info>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Justin Pryzby <pryzby@telsasoft.com>, PostgreSQL Developers <pgsql-hackers@postgresql.org>
Date: 2021-12-01T20:46:40Z
Lists: pgsql-hackers 
Le mer. 1 déc. 2021 à 19:48, Tom Lane <tgl@sss.pgh.pa.us> a écrit :

> Justin Pryzby <pryzby@telsasoft.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.

Commits

  1. Avoid leaking memory during large-scale REASSIGN OWNED BY operations.

  2. Reduce memory consumption for pending invalidation messages.