| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Natalie Wenz <nataliewenz(at)ebureau(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: pg_upgrade and frozen xids |
| Date: | 2018-03-06 23:25:07 |
| Message-ID: | CAH2-Wzn4xaMt+VR5NwH5Z0Nk34FEoyU1pFXOy=arV7LYmH4z-w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Tue, Mar 6, 2018 at 3:12 PM, Natalie Wenz <nataliewenz(at)ebureau(dot)com> wrote:
> What happens to the xid of rows/tables when you upgrade postgres via pg_upgrade?
>
> I upgraded a very large database from 9.6 to 10.1 via pg_upgrade recently, and ever since, the auto vacuum has been busy on a large legacy table that has experienced no changes since the upgrade. If the whole table had been frozen prior to the upgrade, would you expect it to stay frozen?
Yes, you're right to expect it to stay frozen.
I wonder if this is due to a (thankfully relatively benign) bug that
was fixed very recently [1]. Are the relations that autovacuum is
processing materialized views?
[1] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=38b41f182a66b67e36e2adf53d078599b1b65483
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Natalie Wenz | 2018-03-06 23:41:27 | Re: pg_upgrade and frozen xids |
| Previous Message | Natalie Wenz | 2018-03-06 23:12:39 | pg_upgrade and frozen xids |