| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_multixact not getting truncated |
| Date: | 2014-11-20 21:10:31 |
| Message-ID: | 20141120211031.GM1639@alvin.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas wrote:
> On Thu, Nov 20, 2014 at 3:44 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> >> So that we can have two ways to lose data?
> >>
> >> Forbidding connections to a database doesn't prevent XID or MXID wraparound.
> >
> > It does prevent the user from doing anything about it, though, since
> > they can't manually vacuum template0 without knowing unpublished hackery.
>
> True. I don't know what to do about that. Do you?
Maybe tweak autovacuum so that it vacuum-freezes the non-connectable
template databases when they are multixact_freeze_min_age old -- or
something similar. That would cause the multixact age to go down to
zero for those databases with enough frequency.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2014-11-20 21:21:28 | Re: pg_multixact not getting truncated |
| Previous Message | Robert Haas | 2014-11-20 21:03:53 | Re: pg_multixact not getting truncated |