From: Justin Pryzby
Sent: Monday, November 29, 2021 16:10
> On Mon, Nov 29, 2021 at 02:01:35PM +, Arne Roland wrote:
> > But my main goal is something else. I can't explain my clients, why a
> > chanced statistics due to autovacuum suddenly leads to oom. They would be
> > right to question p
On Mon, Nov 29, 2021 at 02:01:35PM +, Arne Roland wrote:
> But my main goal is something else. I can't explain my clients, why a chanced
> statistics due to autovacuum suddenly leads to oom. They would be right to
> question postgres qualification for any serious production system.
What vers
I did read parts of the last one back then. But thanks for the link, I plan to
reread the thread as a whole.
>From what I can tell, the discussions here are the attempt by very smart
>people to (at least partially) solve the problem of memory allocation (without
>sacrificing to much on the run
On Sat, Nov 27, 2021 at 04:33:07PM +, Arne Roland wrote:
> Hello!
>
> Since I used a lot of my time chasing short lived processes eating away big
> chunks of memory in recent weeks, I am wondering about a decent way to go
> about this.
> The problem I am facing essentially relates to the fac
Hello!
Since I used a lot of my time chasing short lived processes eating away big
chunks of memory in recent weeks, I am wondering about a decent way to go about
this.
The problem I am facing essentially relates to the fact that work_mem settings,
while they are enforced per hash and sort node
