pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Matthew T. O'Connor <matthew@zeut.net>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Chris Hoover <revoohc@gmail.com>
Cc: pgsql-admin@postgresql.org Admin <pgsql-admin@postgresql.org>
Subject: Re: More Autovacuum questions
Date: Wed, 16 Jul 2008 01:27:24 -0400
Message-ID: <487D86BC.4020607@zeut.net> (raw)
In-Reply-To: <20080715223635.GC9945@alvh.no-ip.org>
References: <1d219a6f0807150619o567709ebu7d28429d2907bf82@mail.gmail.com>
	<487CBE5E.6030903@zeut.net>
	<20080715223635.GC9945@alvh.no-ip.org>

Alvaro Herrera wrote:
> Matthew T. O'Connor escribió:
>   
>> As Alvaro already said this is a case where autovacuum still isn't  
>> great.
>>     
>
> While I have your attention ;-) do you have any ideas on how to improve
> this?  I don't see anything that looks like a solution for this case.

No good ideas, but a few random thoughts. 
1) Can we make vacuum not block analyze?  That way we can continue to 
analyze a table while it's being vacuumed.
1b) If not, can we make auto-analyze bump auto-vacuum?
2) Maintenance windows.  They wouldn't solve this problem, but they 
might mitigate it some.




view thread (8+ messages)

Message-ID: <487D86BC.4020607@zeut.net>
Permalink:  ../487D86BC.4020607@zeut.net/
Also on:    postgresql.org/message-id/487D86BC.4020607@zeut.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 using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: matthew@zeut.net, alvherre@commandprompt.com, revoohc@gmail.com
  Subject: Re: More Autovacuum questions
  In-Reply-To: <487D86BC.4020607@zeut.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