Re: Lots of memory allocated when reassigning Large Objects

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: Guillaume Lelarge <guillaume(at)lelarge(dot)info>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Lots of memory allocated when reassigning Large Objects
Date: 2021-12-01 18:47:58
Message-ID: 1985969.1638384478@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bossart, Nathan 2021-12-01 18:59:25 Re: XMAX_LOCK_ONLY and XMAX_COMMITTED (fk/multixact code)
Previous Message Bossart, Nathan 2021-12-01 18:33:29 Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file