| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: questions about wraparound |
| Date: | 2021-03-29 17:12:15 |
| Message-ID: | 88d01a3bf0443a78c66ff86e41a9dba94eb06cfb.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 2021-03-29 at 16:58 +0200, Luca Ferrari wrote:
> > If there is no activity on a database, its "datfrozenxid" stays
> > the same. So, as transaction IDs are consumed, it is getting older
> > automatically. That means that even inactive databases will receive
> > an anti-wraparound vacuum occasionally. But that should not have
> > to do anything except advance "datfrozenxid".
>
> Thanks, but this is exactly my point: since inactive databases are
> getting older, why it appears to me that autovacuum is not freezing
> them? I mean, in my experiment age( datfrozenzid) reports the same age
> for every database, even the inactive ones. And since there were
> inactive databases, I was expecting emergency autovacuum to be able to
> run and freeze them. Or am I wrong?
I didn't follow the rest of the thread, but autovacuum should handle
those databases and advance their "datfrozenxid".
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bryn Llewellyn | 2021-03-29 21:48:40 | Re: = t1 - t0 but t0 + i <> t1 when t1 and t2 timestamptz values and i is an interval value |
| Previous Message | Adrian Klaver | 2021-03-29 14:59:11 | Re: search_path in pg_dump output. |