Обсуждение: Analyze makes queries slow...

Поиск
Список
Период
Сортировка

Analyze makes queries slow...

От
Stef
Дата:
Hi all,

I have a problem :

A select statement that selects from 7 tables,
groups the information by 6 columns of the
tables involved.

When there are no rows in pg_statistics,
the query runs under 3 minutes.

When I analyze the biggest table of the 7
(approx 1000000 rows), the query takes longer than
12 Hours (Had to kill it eventually).

I have the explain plan of the original, under 3 minutes
query, and would like to reverse engineer this, to
build up a query with proper join statements, as I understand
that this is a way of forcing the planner to join the table
in a faster way.

I got very close a couple of times, but still can't get it 100%
the same as what the planner did prior to analyzing.

The database is actually faster when analyzed, except
for two or three multiple join queries (which don't finish
after analyze) So I would like to make an exception
for the tables that are used in these queries only,
or do proper joins.

Can anybody help, or give some links to good 
help resources?

TIA
Stefan


Re: Analyze makes queries slow...

От
Jonathan Gardner
Дата:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 06 August 2003 08:18, Stef wrote:
>
> Can anybody help, or give some links to good
> help resources?
>

Try the performance list.

Attach the create statements used to create the tables, the query you are
running, and the different explain plans that were generated. If you know
what it is, you may also want to attach the relevant statistics from the
pg_stats table. They will be most helpful.

- --
Jonathan Gardner <jgardner@jonathangardner.net>
Live Free, Use Linux!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/M87QWgwF3QvpWNwRAgMfAJ9c6O9EyVbJYiguv/b2wtf/NsLZfACgq3lW
YjpMSEMZ4gfyGaGoJcOjpSo=
=4/hA
-----END PGP SIGNATURE-----


Re: Analyze makes queries slow...

От
Stef
Дата:
On Fri, 8 Aug 2003 09:24:48 -0700
Jonathan Gardner <jgardner@jonathangardner.net> wrote:

=> Try the performance list.

Thanks for the tip

Stef