postgres query is very slow

Hi,

I built a database on postgres8.1, then I did VACUUM FULL ANALYZE, but th=
e
query is still slow.
Has anybody an idea ?

Thanks

Dong


--
Sent via pgsql-admin mailing list (pgsql-admin [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
donghe [ Di, 22 Juni 2010 19:23 ] [ ID #2043509 ]

Re: postgres query is very slow

<donghe [at] caltech.edu> wrote:

> I built a database on postgres8.1, then I did VACUUM FULL ANALYZE,
> but the query is still slow.
> Has anybody an idea ?

I recommend you re-post to the pgsql-performance list, after reading
this:

http://wiki.postgresql.org/wiki/SlowQueryQuestions

The one thing I can say based on the information you've provided so
far is that you can expect major performance improvements if you
upgrade to a new major release of PostgreSQL.

Well, there is one other thing -- it's almost never a good idea to
run VACUUM FULL. You may have bloated your indexes. You could try
a REINDEX on the database.

-Kevin

--
Sent via pgsql-admin mailing list (pgsql-admin [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Kevin Grittner [ Di, 22 Juni 2010 19:33 ] [ ID #2043510 ]

Re: postgres query is very slow

<donghe [at] caltech.edu> wrote:

> I built a database on postgres8.1, then I did VACUUM FULL ANALYZE, but
> the query is still slow.
> Has anybody an idea ?

When I had performance problems, what I did was go through the specific
queries that we presenting the performance problem and used an analyze on
those queries. I found that there was a significant performance issues
with the way that some queries were fashioned. What I ended up doing was
switching to 8.2.

-Tino

--
Sent via pgsql-admin mailing list (pgsql-admin [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
tdai [ Mi, 30 Juni 2010 23:03 ] [ ID #2043852 ]
Datenbanken » gmane.comp.db.postgresql.admin » postgres query is very slow

Vorheriges Thema: postgres database user account
Nächstes Thema: cache lookup failed for index