| From: | adey <adey11(at)gmail(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>, "PostgreSQL Admin" <postgres(at)productivitymedia(dot)com>, postgresql-l <postgresql-l(at)groups(dot)ittoolbox(dot)com> |
| Subject: | Re: Fwd: vacuuming template0 gave ERROR |
| Date: | 2006-07-31 02:07:01 |
| Message-ID: | 1c66bda80607301907t53a39d0am77fb6191dbe070a8@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Thanks Tom - datfrozenxid has been the same for at least the last month on
template0 and 1
On 7/31/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> adey <adey11(at)gmail(dot)com> writes:
> > select datname, age(datfrozenxid), datfrozenxid, current_date,
> current_time
> > FROM pg_database
>
> > If template0 shouldn't be touched (and I don't know of deliberate access
> to
> > it), why is this changing please?
>
> Because current xid is changing and template0's datfrozenxid is not.
>
> Nonetheless, if template0 is properly frozen then you don't need to
> vacuum it, regardless of what age(datfrozenxid) says.
>
> regards, tom lane
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aaron Bono | 2006-07-31 04:30:57 | Re: Scheduled backup in postgresql |
| Previous Message | Tom Lane | 2006-07-31 01:30:24 | Re: Fwd: vacuuming template0 gave ERROR |