Postgres Pro
Downloads
Home   >   mailing lists

Re: Bug fix. autovacuum.c do_worker_start() associates memory allocations with TopMemoryContext rather than 'Autovacuum start worker (tmp)' - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Bug fix. autovacuum.c do_worker_start() associates memory allocations with TopMemoryContext rather than 'Autovacuum start worker (tmp)'
Date
Msg-id 20220831200922.52yhz43m7lcimihl@awork3.anarazel.de
Whole thread Raw
In response to Re: Bug fix. autovacuum.c do_worker_start() associates memory allocations with TopMemoryContext rather than 'Autovacuum start worker (tmp)'  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Bug fix. autovacuum.c do_worker_start() associates memory allocations with TopMemoryContext rather than 'Autovacuum start worker (tmp)'
List pgsql-hackers
Tree view 
Hi,

On 2022-08-31 16:05:03 -0400, Tom Lane wrote:
> Even if there's only a visible leak in v15/HEAD, I'm inclined
> to back-patch this all the way, because it's certainly buggy
> on its own terms.  It's just the merest accident that neither
> caller is leaking other stuff into TopMemoryContext, because
> they both think they are using a short-lived context.

+1

> Thanks for the report!

+1

Greetings,

Andres Freund

pgsql-hackers by date:

Previous
From: Jeremy Schneider
Date:
Subject: Re: [PATCH] Query Jumbling for CALL and SET utility statements
Next
From: "Jonathan S. Katz"
Date:
Subject: Re: SQL/JSON features for v15