| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | John R Pierce <pierce(at)hogranch(dot)com> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Postgres is slow |
| Date: | 2005-03-08 17:53:59 |
| Message-ID: | 1110304438.30529.602.camel@state.g2switchworks.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Tue, 2005-03-08 at 11:35, John R Pierce wrote:
> I've found that 7.x pgsql databases periodically need to be pg_dump'd, dropdb,
> then reloaded from the dump to continue to perform well... on a heavy use web
> server database which includes a busy user forum, I find doing this about 2-3
> times a year keeps things smooth. there may be a better way to clean them up,
> but I've not found it.
The most common cause here was index bloat. dropping / recreating the
indexes usually fixes the performance problems. reindex indexname from
the psql command line works well to do this.
note that some usage patterns that cause catalog indexes to bloat can
only be corrected by reindexing while in single user mode.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2005-03-08 18:17:29 | Re: Postgres is slow |
| Previous Message | Prajakt Deolasee | 2005-03-08 17:51:08 | Re: Postgres is slow |