pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: David Rowley <david.rowley@2ndquadrant.com>
Cc: Peter Geoghegan <pg@bowt.ie>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Joe Conway <mail@joeconway.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Should we increase the default vacuum_cost_limit?
Date: Wed, 6 Mar 2019 21:26:49 +0100
Message-ID: <973536be-26a8-5857-430d-07cda99ee5b4@2ndquadrant.com> (raw)
In-Reply-To: <CAKJS1f9jEwsMeX22wh-T5_D9UPF-16Gjhq4=eEg9Aphc6WjG1A@mail.gmail.com>
References: <CAKJS1f_YbXC2qTMPyCbmsPiKvZYwpuQNQMohiRXLj1r=8_rYvw@mail.gmail.com>
	<CAH2-Wz=WQ9ju6sjPF7RcW0g6NPXAenZeC5qVme6uj+eMRw5q2g@mail.gmail.com>
	<241b80ab-7af0-c606-7b2c-b0a5d6be696a@joeconway.com>
	<CAKJS1f_5xofbg0K16MkhQPeCXV6oGCuD2SVcV76OW7ydFDHDkw@mail.gmail.com>
	<CA+Tgmoas1AbDQPAoE1yE9U7d56j06swZvickKKfoYjUoM3t6UQ@mail.gmail.com>
	<CAH2-WzkauoNo3TmWjWwTHRZPVaw1=VB51E8W3BRm5Zx4AVEByw@mail.gmail.com>
	<c5a2de9d-ded2-5876-5420-d1f6190ff352@2ndquadrant.com>
	<CAKJS1f9jEwsMeX22wh-T5_D9UPF-16Gjhq4=eEg9Aphc6WjG1A@mail.gmail.com>



On 3/6/19 12:10 AM, David Rowley wrote:
> Thanks for chipping in on this.
> 
> On Wed, 6 Mar 2019 at 01:53, Tomas Vondra <tomas.vondra@2ndquadrant.com> wrote:
>> But on the other hand it feels a bit weird that we increase this one
>> value and leave all the other (also very conservative) defaults alone.
> 
> Which others did you have in mind? Like work_mem, shared_buffers?  If
> so, I mentioned in the initial post that I don't see vacuum_cost_limit
> as in the same category as those.  It's not like PostgreSQL won't
> start on a tiny server if vacuum_cost_limit is too high, but you will
> have issues with too big a shared_buffers, for example.   I think if
> we insist that this patch is a review of all the "how big is your
> server" GUCs then that's raising the bar significantly and
> unnecessarily for what I'm proposing here.
> 

On second thought, I think you're right. It's still true that you need
to bump up various other GUCs on reasonably current hardware, but it's
true vacuum_cost_limit is special enough to increase it separately.

so +1 (I see Andrew already pushed it, but anyway ...)

-- 
Tomas Vondra                  http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services




view thread (44+ messages)  latest in thread

Message-ID: <973536be-26a8-5857-430d-07cda99ee5b4@2ndquadrant.com>
Permalink:  ../973536be-26a8-5857-430d-07cda99ee5b4@2ndquadrant.com/
Also on:    postgresql.org/message-id/973536be-26a8-5857-430d-07cda99ee5b4@2ndquadrant.com

 · 

reply
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: tomas.vondra@2ndquadrant.com, david.rowley@2ndquadrant.com, pg@bowt.ie, robertmhaas@gmail.com, mail@joeconway.com, pgsql-hackers@lists.postgresql.org
  Subject: Re: Should we increase the default vacuum_cost_limit?
  In-Reply-To: <973536be-26a8-5857-430d-07cda99ee5b4@2ndquadrant.com>

* 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