Re: HELP: Urgent, Vacuum problem

Поиск
Список
Период
Сортировка
От Bradley Russell
Тема Re: HELP: Urgent, Vacuum problem
Дата
Msg-id 00e601c7188c$a2f71ba0$4a0a10ac@npci.com
обсуждение исходный текст
Ответ на HELP: Urgent, Vacuum problem  ("Schwenker, Stephen" <SSchwenker@thestar.ca>)
Список pgsql-general
We had the same problem recently on our data warehouse.
 
Check out the reindex and cluster commands.
 
 
-----Original Message-----
From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of Schwenker, Stephen
Sent: Monday, December 04, 2006 9:56 AM
To: pgsql-general@PostgreSQL.org
Subject: [GENERAL] HELP: Urgent, Vacuum problem

Hello,
 
I'm having a major Vacuuming problem.  I used to do a full vacuum every morning on my postgres database to clean up empty space on a table but because of it's size, the locking of the database causes my application server to max out the database connections and causes database errors.  To fix that problem, I have turned off the full vacuum and are just doing a standard analyze vacuum.  No I'm getting very close to running out of space on my disks because the table keeps on growing and the database is not re-using deleted record space.  I know this because I delete 99% of the records from the table after I have exported them but the size of the database tables are not decreasing.  Now I can't shrink the size of the tables because the full vacuum takes too long to run  Over 2 hours and locks the table for too long.
 
Can anyone help me with fixing my problem with vacuuming and disk space?
 
I'm using version 7.4.2 on solaris.
 
Thank you,
 
 
Steve.

В списке pgsql-general по дате отправления:

Предыдущее
От: hugo.wetterberg@gmail.com
Дата:
Сообщение: Working with one live and one development database
Следующее
От: Andreas Kretschmer
Дата:
Сообщение: Re: Ident authentication failed for user - URGENT