Re: pg_autovacuum and REINDEX at the same time (?) - Mailing list pgsql-bugs

From Heikki Linnakangas
Subject Re: pg_autovacuum and REINDEX at the same time (?)
Date
Msg-id 45E571A2.2010209@enterprisedb.com
Whole thread Raw
In response to Re: pg_autovacuum and REINDEX at the same time (?)  (Janar Kartau <janar.kartau@cvkeskus.ee>)
List pgsql-bugs
Janar Kartau wrote:
> I know what causes the "sorry, too many clients already" error, but the
> number of connections shouldn't grow so big.. so i guess the table
> (category_tree) got locked.

If that happens again, take a look at pg_stat_activity or ps output to
see what's going on. Something must be using the connections, a locked
table alone won't give you that error message.

> We do REINDEX every 5 minutes because the table gets updated very often
> and the query's took a lot of time. I think since we use autovacuum now,
> it's not needed anymore.

Yeah, a vacuum is normally enough to keep the indexes in good shape. I'd
  suggest removing the REINDEX call and either letting autovacuum handle
it, or adding an explicit VACUUM call after the commit.

--
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com

pgsql-bugs by date:

Previous
From: Janar Kartau
Date:
Subject: Re: pg_autovacuum and REINDEX at the same time (?)
Next
From: Rob Schall
Date:
Subject: Problem with an Identical Query