Re: Lots of memory allocated when reassigning Large Objects - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Lots of memory allocated when reassigning Large Objects
Date
Msg-id 1985969.1638384478@sss.pgh.pa.us
Whole thread Raw
In response to Lots of memory allocated when reassigning Large Objects  (Guillaume Lelarge <guillaume@lelarge.info>)
Responses Re: Lots of memory allocated when reassigning Large Objects  (Guillaume Lelarge <guillaume@lelarge.info>)
List pgsql-hackers
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.

            regards, tom lane



pgsql-hackers by date:

Previous
From: "Bossart, Nathan"
Date:
Subject: Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file
Next
From: "Bossart, Nathan"
Date:
Subject: Re: XMAX_LOCK_ONLY and XMAX_COMMITTED (fk/multixact code)