pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Iain <iain@mst.co.jp>
To: 'Edoardo Ceccarelli' <eddy@axa.it>
Cc: pgsql-admin@postgresql.org
Subject: Re: R: slow seqscan after vacuum analize
Date: Thu, 5 Feb 2004 15:32:29 +0900
Message-ID: <006401c3ebb1$d4237c60$7201a8c0@mst1x5r347kymb> (raw)
References: <2s28b9$kqpmo@mailr-1.tiscali.it>



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

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.




view thread (6+ messages)  latest in thread

Message-ID: <006401c3ebb1$d4237c60$7201a8c0@mst1x5r347kymb>
Permalink:  ../006401c3ebb1$d4237c60$7201a8c0@mst1x5r347kymb/
Also on:    postgresql.org/message-id/006401c3ebb1$d4237c60$7201a8c0@mst1x5r347kymb

 · 

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: iain@mst.co.jp, eddy@axa.it
  Subject: Re: R: slow seqscan after vacuum analize
  In-Reply-To: <006401c3ebb1$d4237c60$7201a8c0@mst1x5r347kymb>
  References: <2s28b9$kqpmo@mailr-1.tiscali.it> <006401c3ebb1$d4237c60$7201a8c0@mst1x5r347kymb>

* 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