| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Removing more vacuumlazy.c special cases, relfrozenxid optimizations |
| Date: | 2022-03-31 04:29:16 |
| Message-ID: | CAH2-WzmN4qh04TcyNph8=1awdUN-nzza_6y+TRbEo-ECiCDV0w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 30, 2022 at 9:20 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> But the debug elog reports that
>
> relfrozenxid updated 714 -> 717
> relminmxid updated 1 -> 6
>
> Tthe problem is that the crashing backend reads the relfrozenxid/relminmxid
> from the shared relcache init file written by another backend:
We should have added logging of relfrozenxid and relminmxid a long time ago.
> This is basically the inverse of a54e1f15 - we read a *newer* horizon. That's
> normally fairly harmless - I think.
Is this one pretty old?
> Perhaps we should just fetch the horizons from the "local" catalog for shared
> rels?
Not sure what you mean.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2022-03-31 04:44:32 | Re: Removing more vacuumlazy.c special cases, relfrozenxid optimizations |
| Previous Message | Andres Freund | 2022-03-31 04:24:43 | Re: Removing more vacuumlazy.c special cases, relfrozenxid optimizations |