On Thu, Feb 2, 2012 at 4:33 AM, Alvaro Herrera <alvhe...@alvh.no-ip.org> wrote:
> However, there are cases where not even that is possible -- consider > tuple freezing during WAL recovery. Recovery is going to need to > replace those multis with other multis, but it cannot create new multis > itself. The only solution here appears to be that when multis are > frozen in the master, replacement multis have to be logged too. So the > heap_freeze_tuple Xlog record will have a map of old multi to new. That > way, recovery can just determine the new multi to use for any particular > old multi; since multixact creation is also logged, we're certain that > the replacement value has already been defined. Multixacts are ignored during recovery. Why do anything at all? -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers