pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Matt Clark <matt@ymogen.net>
To: scott.marlowe <scott.marlowe@ihs.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Is there a reason _not_ to vacuum continuously?
Date: Wed, 17 Sep 2003 21:20:02 +0100
Message-ID: <LFEIJBEOKGPDHCEMDGNFKECGCDAA.matt@ymogen.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0309171353490.8026-100000@css120.ihs.com>

Yes, that makes sense.  My worry is really the analyzes.  I gather/imagine
that:

1)	Indexes on fields that are essentially random gain little from being
analyzed.
2)	Fields that increase monotonically with insertion order have a problem
with index growth in 7.2.  There may be a performance issue connected with
this, although indexes on these fields also gain little from analysis.  So
if I can't vacuum full I'm SOL anyway and should upgrade to 7.4.1 when
available?

Further data:  When I run a vacuum analyze my app servers do see an increase
in response time from PG, even though the DB server is under no more
apparent load.  I can only assume some kind of locking issue.  Is that fair?

M





> -----Original Message-----
> From: pgsql-performance-owner@postgresql.org
> [mailto:pgsql-performance-owner@postgresql.org]On Behalf Of
> scott.marlowe
> Sent: 17 September 2003 20:55
> To: Matt Clark
> Cc: pgsql-performance@postgresql.org
> Subject: Re: [PERFORM] Is there a reason _not_ to vacuum continuously?
>
>
> On Wed, 17 Sep 2003, Matt Clark wrote:
>
> > *** THE QUESTION(S) ***
> > Is there any reason for me not to run continuous sequential
> vacuum analyzes?
> > At least for the 6 tables that see a lot of updates?
> > I hear 10% of tuples updated as a good time to vac-an, but does
> my typical
> > count of 3 indexes per table affect that?
>
> Generally, the only time continuous vacuuming is a bad thing is when you
> are I/O bound.  If you are CPU bound, then continuous vacuuming
> is usually
> acceptable.
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
>       joining column's datatypes do not match
>




view thread (14+ messages)  latest in thread

Message-ID: <LFEIJBEOKGPDHCEMDGNFKECGCDAA.matt@ymogen.net>
Permalink:  ../LFEIJBEOKGPDHCEMDGNFKECGCDAA.matt@ymogen.net/
Also on:    postgresql.org/message-id/LFEIJBEOKGPDHCEMDGNFKECGCDAA.matt@ymogen.net

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: matt@ymogen.net, scott.marlowe@ihs.com
  Subject: Re: Is there a reason _not_ to vacuum continuously?
  In-Reply-To: <LFEIJBEOKGPDHCEMDGNFKECGCDAA.matt@ymogen.net>
  References: <Pine.LNX.4.33.0309171353490.8026-100000@css120.ihs.com> <LFEIJBEOKGPDHCEMDGNFKECGCDAA.matt@ymogen.net>

* 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