Postgres Pro
Downloads
Home   >   mailing lists

Thread: 8.0.0beta3 vacuum analyze

8.0.0beta3 vacuum analyze

From
"Ed L."
Date:
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

Ed

Re: 8.0.0beta3 vacuum analyze

From
Neil Conway
Date:
On Mon, 2004-10-18 at 14:49, 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?

No.

> #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

Vacuum cost delay affects the way that VACUUM behaves, not the frequency
with which it is executed.

-Neil

Re: 8.0.0beta3 vacuum analyze

From
Christopher Browne
Date:
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

Re: 8.0.0beta3 vacuum analyze

From
Jan Wieck
Date:
On 10/18/2004 12:49 AM, 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?

Are you running Slony by any chance?


Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #

Re: 8.0.0beta3 vacuum analyze

From
"Ed L."
Date:
On Monday October 18 2004 2:39, Jan Wieck wrote:
> On 10/18/2004 12:49 AM, 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?
>
> Are you running Slony by any chance?

Not on the system in question.  Problem has ceased.

Ed