| From: | Jose Manuel Garcia Valladolid <garcia_josval(at)gva(dot)es> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Cc: | Jose Alarcon <alarcon_jos(at)gva(dot)es> |
| Subject: | WAL configuration and REINDEX |
| Date: | 2006-09-21 10:40:55 |
| Message-ID: | 45126C37.6020106@gva.es |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hello admins,
I have a PostgreSQL 8.1.4 server under Linux Red Hat with several
databases. The server is configured with WAL archiving turned on. As a
maintenance process, every night one cron job launches a backup process
to the server with
pg_dump, then the server shuts down and starts up and do a REINDEX
DATABASE to all databases to keep all tables reindexed.
After 30 days of no activity to the server (this is a DBA test server)
the amount of WAL segments is increasing at very high speed. Every
REINDEX process generates between 25 and 30 WAL segments. With this
behavior (and no activity!!) I can not maintain this amount of data to
performs future WAL backups and recovers.
Any idea to decrease the number of WAL segments generated?
Is possible to know when a table would be reindexed and to avoid dayly
REINDEX process?
Thank you.
Jose Manuel García V.
| Attachment | Content-Type | Size |
|---|---|---|
| garcia_josval.vcf | text/x-vcard | 451 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mr. Dan | 2006-09-21 15:45:06 | psql: FATAL: the database system is starting up |
| Previous Message | Michael Fuhr | 2006-09-21 02:51:12 | Re: Beginning SSL Questions |