| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(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:03:53 |
| Message-ID: | CA+TgmoaoRaE0a9RkPNQDi-fN9dKEBCt=Pt37h5i0Y8m8RedbXA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2014-11-20 21:10:31 | Re: pg_multixact not getting truncated |
| Previous Message | Peter Geoghegan | 2014-11-20 20:57:24 | Re: Doing better at HINTing an appropriate column within errorMissingColumn() |