Re: We probably need autovacuum_max_wraparound_workers - Mailing list pgsql-hackers

From Tom Lane
Subject Re: We probably need autovacuum_max_wraparound_workers
Date
Msg-id 11195.1340891516@sss.pgh.pa.us
Whole thread Raw
In response to Re: We probably need autovacuum_max_wraparound_workers  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: We probably need autovacuum_max_wraparound_workers  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Thu, Jun 28, 2012 at 2:02 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Well, that's a fair point, but I don't think it has anything to do with
>> Josh's complaint --- which AFAICT is about imposed load, not about
>> failure to vacuum things that need vacuumed.

> I think it's got everything to do with it.  Josh could fix his problem
> by increasing the cost limit and/or reducing the cost delay, but if he
> did that then his database would get bloated...

Josh hasn't actually explained what his problem is, nor what if any
adjustments he made to try to ameliorate it.  In the absence of data
I refuse to rule out misconfiguration.  But, again, to the extent that
he's given us any info at all, it seemed to be a complaint about
oversaturated I/O at max load, *not* about inability to complete
vacuuming tasks as needed.  You are inventing problem details to fit
your solution.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [Review] Add SPI_gettypmod() to return a field's typemod from a TupleDesc
Next
From: Robert Haas
Date:
Subject: Re: We probably need autovacuum_max_wraparound_workers