| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(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:21:28 |
| Message-ID: | 546E5B58.2010904@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/20/2014 01:03 PM, 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?
Well, the first thing that comes to mind is that template0 should be
"permanently frozen". That is, all objects in it should be created with
frozen xid and mxids. After all, nobody can modify anything in it.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2014-11-20 21:42:15 | Re: INSERT ... ON CONFLICT {UPDATE | IGNORE} |
| Previous Message | Alvaro Herrera | 2014-11-20 21:10:31 | Re: pg_multixact not getting truncated |