On Mon, 10 Sep 2001 [EMAIL PROTECTED] wrote:
> Use explain. Explain tells you the query plan of the optimizer.
>
> explain SELECT .....;
Thanks I just found the thread "Index usage question" and tried to make
some profit from it:
explain SELECT Hauptdaten_Fall.MeldeKategorie, Count(Hauptdaten_Fall.ID) AS Anz FROM
Hauptdaten_Fall WHERE (((Hauptdaten_Fall.IstAktuell)=20)) GROUP BY
Hauptdaten_Fall.MeldeKategorie ORDER BY Hauptdaten_Fall.MeldeKategorie;
NOTICE: QUERY PLAN:
Aggregate (cost=35267.33..36154.62 rows=17746 width=16)
-> Group (cost=35267.33..35710.98 rows=177458 width=16)
-> Sort (cost=35267.33..35267.33 rows=177458 width=16)
-> Seq Scan on hauptdaten_fall (cost=0.00..15024.12 rows=177458
width=16)
Now I tried
Vacuum analyze;
but nothing changed :-(
Aggregate (cost=35267.33..36154.62 rows=17746 width=16)
-> Group (cost=35267.33..35710.98 rows=177458 width=16)
-> Sort (cost=35267.33..35267.33 rows=177458 width=16)
-> Seq Scan on hauptdaten_fall (cost=0.00..15024.12 rows=177458
width=16)
I have nearly no experience with query optimizing but the gread difference
in speed tells me that something is wrong here. There were some hints in
the "Index usage question" thread about some fields which might be interpreted
as strings. Could this be a reason and how to check this?
Kind regards
Andreas.
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
