Re: pg_clog & vacuum oddness
От | DHS Webmaster |
---|---|
Тема | Re: pg_clog & vacuum oddness |
Дата | |
Msg-id | 3F9FF647.D3759159@dhs-club.com обсуждение исходный текст |
Ответ на | pg_clog & vacuum oddness (Jeff <threshar@torgo.978.org>) |
Список | pgsql-admin |
Well, you know, I looked at the list and saw only template0, template1 & our working DB. So just for kicks I vacuumed template1. That cleared the directory. To my knowledge we did not modify template1 one when we setup the database initially, so perhaps it just needed a vacuum to set the stage correctly. Either that or during our data import, there was something in the import file that referenced template1 which created a need for vacuuming. Whatever the case, this was an interesting exercise which I'm sure will prove useful in the future. Thank you. -- Bill MacArthur Webmaster DHS Club Jeff wrote: > > On Wed, 29 Oct 2003 11:53:38 -0500 > DHS Webmaster <webmaster@dhs-club.com> wrote: > > > We vacuum our working database nightly. Although this is not a 'full', > > we don't exclude any tables. We don't do anything with template1 > > (knowingly), so we do not perform any maintenance on it either. > > Why not go through the list in pg_database to make sure you didn't > forget about any (like I did). > > given that template0 and 1 rarely change.. I don't see why we'd need to > vacuum them > > -- > Jeff Trout <jeff@jefftrout.com> > http://www.jefftrout.com/ > http://www.stuarthamm.net/
В списке pgsql-admin по дате отправления: