From: Edoardo Ceccarelli <eddy@axa.it>
To: 'Sam Barnett-Cormack' <s.barnett-cormack@lancaster.ac.uk>
Cc: pgsql-admin@postgresql.org
Subject: R: R: slow seqscan after vacuum analize
Date: Thu, 5 Feb 2004 02:06:53 +0100
Message-ID: <2s28b9$kqljc@mailr-1.tiscali.it> (raw)
In-Reply-To: <Pine.LNX.4.50.0402050055510.13707-100000@short.lancs.ac.uk>
> ----------------------------------------------------------------------
> > ----------------
> > --------------------
> > Seq Scan on utente (cost=0.00..92174.50 rows=3 width=724) (actual
> > time=705.41..6458.19 rows=15 loops=1)
> > Filter: (luogorilasciodoc = 'ciao'::bpchar) Total
> runtime: 6458.29
> > msec
> > (3 rows
> >
> > Things are worst only for seqscan, when it uses indexscan
> timing is good.
>
> Only thing I can think of is if storage method had been
> changed. Not sure if that would even affect it, or if it
> could do that by itself.
> Just brainstorming.
>
Do you know how can I check if the storage method has changed?
I was thinking that the priority target of a vacuum operation is to reclaim disk space
- this might imply that the performance are worst for a seqscan - maybe it's normal.
Anyway, I am doing a VACUUM FULL ANALYZE right now to see if things get better.
Thanks for you hints
Edoardo
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: eddy@axa.it, s.barnett-cormack@lancaster.ac.uk
Subject: Re: R: R: slow seqscan after vacuum analize
In-Reply-To: <2s28b9$kqljc@mailr-1.tiscali.it>
References: <Pine.LNX.4.50.0402050055510.13707-100000@short.lancs.ac.uk> <2s28b9$kqljc@mailr-1.tiscali.it>
* 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