Re: Optimize querry sql

From: "A(dot) Kretschmer" <andreas(dot)kretschmer(at)schollglas(dot)com>
To: pgsql-sql(at)postgresql(dot)org
Subject: Re: Optimize querry sql
Date: 2007-09-14 11:55:12
Message-ID: 20070914115512.GD7443@a-kretschmer.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

am Fri, dem 14.09.2007, um 12:26:00 +0200 mailte Stanislas de Larocque folgendes:
> Hi,
>
> Explain my sql querry :
>
> Limit (cost=1057.15..1057.16 rows=1 width=27)
> -> HashAggregate (cost=1057.15..1057.16 rows=1 width=27)
> -> Nested Loop (cost=0.00..1057.14 rows=1 width=27)
> -> Seq Scan on stat a (cost=0.00..1042.98 rows=1 width=8)
> Filter: (((month)::double precision =
> date_part('month'::text, (now() - '1 mon'::interval))) AND
> ((year)::double precision = date_part('year'::text, (now() - '1
> mon'::interval))))
> -> Index Scan using resaller_pkey on revendeur b
> (cost=0.00..14.15 rows=1 width=23)
> Index Cond: ("outer".idxresaller = b.idxresaller)
> Filter: (asp = 6)
>
> I would optimize "Seq Scan on stat a (cost=0.00..1042.98 rows=1 width=8)"
>
> What is your advice ?

Create indexes on the columns month and year. But, again, you have an
unpractical table-design.

>
> Thank you
>
> Stan
>
>
> 2007/9/14, A. Kretschmer <andreas(dot)kretschmer(at)schollglas(dot)com>:

Please no top-posting.
(answer on top and fullquote below)

Andreas
--
Andreas Kretschmer
Kontakt: Heynitz: 035242/47150, D1: 0160/7141639 (mehr: -> Header)
GnuPG-ID: 0x3FFF606C, privat 0x7F4584DA http://wwwkeys.de.pgp.net

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message hubert depesz lubaczewski 2007-09-14 11:59:32 Re: Optimize querry sql
Previous Message Stanislas de Larocque 2007-09-14 10:26:00 Re: Optimize querry sql