Hi all,

I have a database that I made a copy of (useing pg_dump) to test a new
program on. The program runs just fine on the new(copy) database. However,
when I switched my program to run on my old(original) database it runs
around 10 times slower and takes up way more processor power. I tried
vacuumdb on the old database and it made no difference. Any idea what my
problem might be? I could just drop and restore the old database, but I
would really like to understand what might be going on so I could watch for
it in the future and hopefully prevent it from happening again.

Any information is greatly appreciated.

Jason Haselbauer
Soundconcept.net
jason (AT) soundconcept (DOT) net



---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly

On Wednesday 01 September 2004 1:59 pm, jason (AT) soundconcept (DOT) net wrote:
If the original database isn't live then try a vacuum full on the old
database and be sure to analyze it as well (vacuumdb --full
--analyze). The standard vacuum does not physically shrink the
database files - it just makes no longer used space within the file
available for reuse. The --analyze will update the statistics the
planner uses when deciding how to approach the query (mainly use of
indexes).

If that doesn't do the trick, try reindexing the tables.

Cheers,
Steve

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html