| From: | DHS Webmaster <webmaster(at)dhs-club(dot)com> |
|---|---|
| To: | Jeff <threshar(at)torgo(dot)978(dot)org> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: pg_clog & vacuum oddness |
| Date: | 2003-10-29 17:17:59 |
| Message-ID: | 3F9FF647.D3759159@dhs-club.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)dhs-club(dot)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(at)jefftrout(dot)com>
> http://www.jefftrout.com/
> http://www.stuarthamm.net/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-10-29 17:23:17 | Re: pg_clog & vacuum oddness |
| Previous Message | Jeff | 2003-10-29 17:01:16 | Re: pg_clog & vacuum oddness |