Re: [HACKERS] Rethinking autovacuum.c memory handling - Mailing list pgsql-hackers

From Bossart, Nathan
Subject Re: [HACKERS] Rethinking autovacuum.c memory handling
Date
Msg-id 2E010582-FC1A-49E3-9256-F65DC9823219@amazon.com
Whole thread Raw
In response to Re: [HACKERS] Rethinking autovacuum.c memory handling  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 9/23/17, 12:36 PM, "Tom Lane" <tgl@sss.pgh.pa.us> wrote:
>"Bossart, Nathan" <bossartn@amazon.com> writes:
>> This looks reasonable to me as well.  I haven't noticed any issues after
>> a couple hours of pgbench with aggressive autovacuum settings, either.
>
> Thanks for looking.  As I'm sure you realize, what motivated that was
> not liking the switch into AutovacMemCxt that you'd added in
> autovacuum_do_vac_analyze ... with this patch, we can drop that.

Yup.  I’ll go ahead and update that patch now.

Nathan



--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Rethinking autovacuum.c memory handling
Next
From: Andrew Dunstan
Date:
Subject: Re: [HACKERS] [BUGS] BUG #14825: enum type: unsafe use?