This is occurring In an 8.4.2 pg database, and I have noticed it in 8.3.10 as well.
We do a lot of work with temp tables here, and over time a lot of pg_temp_[n] schemas have appeared.
Similarly, we notice build-up of pg_toast_[n] schemas.
Is it ok to drop these if they contain no tables?
Or is there a way to prevent them from persisting past a given life-time??
Mr
Mark Rostron <mrostron@ql2.com> writes:
> We do a lot of work with temp tables here, and over time a lot of pg_temp_[n] schemas have appeared.
> Similarly, we notice build-up of pg_toast_[n] schemas.
This is expected. There'll be one for each backend slot that's ever
used any temp tables.
> Is it ok to drop these if they contain no tables?
It's risky: you have the race condition that some backend might be just
starting to use a temp schema when you decide to blow away the schema.
It's also pretty pointless, since the schema will just come back again
next time it's needed. I'd say just ignore the temp schemas.
regards, tom lane
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера