Re: Should we increase the default vacuum_cost_limit? - Mailing list pgsql-hackers

From Joe Conway
Subject Re: Should we increase the default vacuum_cost_limit?
Date
Msg-id 241b80ab-7af0-c606-7b2c-b0a5d6be696a@joeconway.com
Whole thread Raw
In response to Re: Should we increase the default vacuum_cost_limit?  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: Should we increase the default vacuum_cost_limit?  (David Rowley <david.rowley@2ndquadrant.com>)
List pgsql-hackers
On 2/25/19 1:17 AM, Peter Geoghegan wrote:
> On Sun, Feb 24, 2019 at 9:42 PM David Rowley
> <david.rowley@2ndquadrant.com> wrote:
>> The current default vacuum_cost_limit of 200 seems to be 15 years old
>> and was added in f425b605f4e.
>>
>> Any supporters for raising the default?
> 
> I also think that the current default limit is far too conservative.

I agree entirely. In my experience you are usually much better off if
vacuum finishes quickly. Personally I think our default scale factors
are horrible too, especially when there are tables with large numbers of
rows.

Joe

-- 
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: INSERT ... OVERRIDING USER VALUE vs GENERATED ALWAYS identitycolumns
Next
From: Stephen Frost
Date:
Subject: Re: Remove Deprecated Exclusive Backup Mode