pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedReally slow even after vacuum
2+ messages / 2 participants
[nested] [flat]
* Really slow even after vacuum
@ 2004-01-21 09:34 Jeroen Baekelandt <jbaekelandt@kiala.com>
2004-01-21 10:42 ` Re: Really slow even after vacuum Dennis Bjorklund <db@zigo.dhs.org>
0 siblings, 1 reply; 2+ messages in thread
From: Jeroen Baekelandt @ 2004-01-21 09:34 UTC (permalink / raw)
To: pgsql-performance
Hi,
I must have missed something, because I get really slow performance from
PG 7.3.4-RH. This is my situation: I have a table (jms_messages), which
contains 500.000 records. select count(*) from jms_messages is
understandable quite slow. Then I delete all of the records and add 1000
new ones. I run vacuumdb on this database and run select count(*) from
jms_messages again. It takes 80 seconds!?! While before, with 1000
records, it took only a fraction of a second.
Thanks for any tips,
Jeroen Baekelandt
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Really slow even after vacuum
2004-01-21 09:34 Really slow even after vacuum Jeroen Baekelandt <jbaekelandt@kiala.com>
@ 2004-01-21 10:42 ` Dennis Bjorklund <db@zigo.dhs.org>
0 siblings, 0 replies; 2+ messages in thread
From: Dennis Bjorklund @ 2004-01-21 10:42 UTC (permalink / raw)
To: Jeroen Baekelandt <jbaekelandt@kiala.com>; +Cc: pgsql-performance
On Wed, 21 Jan 2004, Jeroen Baekelandt wrote:
> jms_messages again. It takes 80 seconds!?! While before, with 1000
> records, it took only a fraction of a second.
run: VACUUM FULL ANALYZE;
--
/Dennis Björklund
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2004-01-21 10:42 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-01-21 09:34 Really slow even after vacuum Jeroen Baekelandt <jbaekelandt@kiala.com>
2004-01-21 10:42 ` Dennis Bjorklund <db@zigo.dhs.org>
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