| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | John Sidney-Woollett <johnsw(at)wardbrook(dot)com> |
| Cc: | postgres general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: vacuum confusion |
| Date: | 2005-02-11 09:25:56 |
| Message-ID: | 420C7A24.1030309@archonet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
John Sidney-Woollett wrote:
> I've got a 7.4.6 db running on linux where we've been vacuuming "full"
> the database each night, and have recently switched to "vacuum analyse"
> instead.
>
> We keep seeing this message at the end of the vacuum run:
>
> WARNING: some databases have not been vacuumed in 2013308218 transactions
> HINT: Better vacuum them within 134175429 transactions, or you may have
> a wraparound failure.
> VACUUM
>
> Why are we seeing this message when the only databases in this cluster
> is the one we are vacuuming (each night), and template0 and template1?
>
> Is there something that we're not doing right?
Are you doing template0/1 too? The transaction IDs are shared between
all databases AFAIK. Before the numbers wrap-around any "low" numbers
need to be replaced by a "frozen" marker (I think it's 0 or 1).
--
Richard Huxton
Archonet Ltd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Postgre.News.Firma | 2005-02-11 09:30:11 | Re: ADO adCmdStoredProc PlPgSql-SP Parameters |
| Previous Message | John Sidney-Woollett | 2005-02-11 07:36:22 | vacuum confusion |