Re: 8.0.0beta3 vacuum analyze - Mailing list pgsql-general

From Christopher Browne
Subject Re: 8.0.0beta3 vacuum analyze
Date
Msg-id m3mzykdwd5.fsf@knuth.knuth.cbbrowne.com
Whole thread Raw
In response to 8.0.0beta3 vacuum analyze  ("Ed L." <pgsql@bluepolka.net>)
List pgsql-general
In the last exciting episode, pgsql@bluepolka.net ("Ed L.") wrote:
> I *think* I'm seeing "vacuum analyze" queries launched automatically on an
> 8.0.0beta3 (unless I have a rogue autovac running that I haven't spotted).
> Is this something new in 8.0 and to be expected?
>
> My settings:
>
> #vacuum_cost_delay = 0        # 0-1000 milliseconds
> #vacuum_cost_page_hit = 1       # 0-10000 credits
> #vacuum_cost_page_miss = 10     # 0-10000 credits
> #vacuum_cost_page_dirty = 20    # 0-10000 credits
> #vacuum_cost_limit = 200        # 0-10000 credits

None of this would cause vacuums to be initiated.

The above configuration settings allow making vacuums "relatively
lazy;" instead of them running full-bore, and killing cache/chewing
I/O, they can do a few blocks worth of work, and then sleep a bit.

They are all commented out, so they won't have _any_ effect.

Note that this "lazier vacuuming" can be run alongside ARC to get some
synergistic benefit:

 - ARC prevents vacuums from trashing the shared memory cache;

 - "lazy vacuum" / "vacuum delay" prevents vacuums from taking over
   all I/O
--
let name="cbbrowne" and tld="linuxfinances.info" in String.concat "@" [name;tld];;
http://www3.sympatico.ca/cbbrowne/
Fatal Error: Found [MS-Windows] System -> Repartitioning Disk for
Linux...
-- <cbbrowne@hex.net> Christopher Browne

pgsql-general by date:

Previous
From: nd02tsk@student.hig.se
Date:
Subject: How to time several queries?
Next
From: Bruno Wolff III
Date:
Subject: Re: Avoiding sequential scans with OR join condition