"Gauri Kanekar" <meetgaurikanekar@gmail.com> writes:

> Befor doing vaccum full on the database this query use to take less
> than 4min. But now after doing vacumming reindexing the tables it is
> taking 73mins.

Vacuum full is generally not necessary. You do need to ensure regular vacuum
is run frequently on heavily updated tables though.

> After observing the explain analyse it seems like it is not selecting
> the required index properly.
>
> So can anybody suggest any thing??

-> Bitmap Index Scan on campaign_attributes_pk (cost=0.00..105.83 rows=60 width=0) (actual time=1.721..1.721 rows=1279 loops=1)

When's the last time you analyzed your tables? Postgres is guessing it'll find
60 rows and instead finding over a thousands rows...

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com


---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org