pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andrew Biagioni <andrew.biagioni@e-greek.net>
To: Iain <iain@mst.co.jp>
Cc: Edoardo Ceccarelli <eddy@axa.it>
Cc: pgsql-admin@postgresql.org
Subject: Re: R: slow seqscan after vacuum analize
Date: Thu, 05 Feb 2004 11:23:34 -0500
Message-ID: <40226E06.2080701@e-greek.net> (raw)
In-Reply-To: <006401c3ebb1$d4237c60$7201a8c0@mst1x5r347kymb>
References: <2s28b9$kqpmo@mailr-1.tiscali.it>
	<006401c3ebb1$d4237c60$7201a8c0@mst1x5r347kymb>

Iain wrote:

>  
>
>>Yes, you are right but it wasn't the case this time, I have run the
>>    
>>
>explain plenty of
>  
>
>>times with same results. I think that the reason was that I made a simple
>>    
>>
>VACUUM,
>  
>
>>after a VACUUM FULL ANALYZE (1h!!) things are ok
>>    
>>
>
>It's reasonable to expect that a seq scan will perform faster after a full
>vacuum, as the physical size and organization of the table has been changed.
>
>I wouldn't expact a plain vacuum to have any tangible affect on performance,
>for the better or for the worse..
>  
>
A plain VACUUM (without ANALYZE) will change the layout of the data 
without refreshing the optimizer information, so that anything that DOES 
use the optimizer will often be negatively affected;  VACUUM ANALYZE 
does a vacuum AND refreshes the optimizer information. 

I usually run VACUUM ANALYZE on an hourly basis on our production 
system, and it's fast enough and unobtrusive enough that I can't tell 
that it's running (except by looking at the log, of course).

>I'd like to know more about the possibility of plain vacuums harming
>performance. This is the first I've heard of it. Vacuum full is not always
>an option in a production environment.
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 7: don't forget to increase your free space map settings
>

view thread (6+ messages)

Message-ID: <40226E06.2080701@e-greek.net>
Permalink:  ../40226E06.2080701@e-greek.net/
Also on:    postgresql.org/message-id/40226E06.2080701@e-greek.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-admin@postgresql.org
  Cc: andrew.biagioni@e-greek.net, iain@mst.co.jp, eddy@axa.it
  Subject: Re: R: slow seqscan after vacuum analize
  In-Reply-To: <40226E06.2080701@e-greek.net>
  References: <2s28b9$kqpmo@mailr-1.tiscali.it> <006401c3ebb1$d4237c60$7201a8c0@mst1x5r347kymb> <40226E06.2080701@e-greek.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