| От | Christoph Frick |
|---|---|
| Тема | Re: large duplicated files |
| Дата | |
| Msg-id | 20070817083707.GJ9296@byleth.sc-networks.de обсуждение |
| Ответ на | Re: large duplicated files ("Ryan D. Enos" <renos@ucla.edu>) |
| Список | pgsql-novice |
On Fri, Aug 17, 2007 at 12:15:13AM -0700, Ryan D. Enos wrote: > Well, I feel like the guy who goes to the doctor and then finds the > pain is suddenly gone when he gets there. I have discovered that my > previously described problem was almost certainly the result of > temporary tables that were not being dropped after a crash through an > OBDC connection (at least I hope that's where those files were coming > from). However, I am still curious if anybody knows how I can find > and destroy those tables in the even of a crash? there are lots of scripts out there (google them) to find out which table/index actually uses up your harddisk space. in an older postgreslql version e.g. an index went nuts and kept growing without reason - reindexing helped here. if you delete lots of data also be sure to vacuum the db (depending on your version of the db) and have enough fsm configured. do a verbose vacuum to find out if there there are enough fsm (shows up at the end of the report). -- cu
В списке pgsql-novice по дате отправления:
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера