From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bossart, Nathan <bossartn@amazon.com>
Cc: Michael Paquier <michael.paquier@gmail.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Subject: Re: Rethinking autovacuum.c memory handling
Date: Sat, 23 Sep 2017 13:36:23 -0400
Message-ID: <15155.1506188183@sss.pgh.pa.us> (raw)
In-Reply-To: <9E08B120-31DE-4B47-9C44-305619F3195C@amazon.com>
References: <13849.1506114543@sss.pgh.pa.us>
<CAB7nPqTosuvT2Pjz5136jAi2+h0gGsYynuUP52Ejrw=JKXxi-Q@mail.gmail.com>
<9E08B120-31DE-4B47-9C44-305619F3195C@amazon.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
"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.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, bossartn@amazon.com, michael.paquier@gmail.com, alvherre@2ndquadrant.com
Subject: Re: Rethinking autovacuum.c memory handling
In-Reply-To: <15155.1506188183@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox