Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts - Mailing list pgsql-bugs

From Tom Lane
Subject Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts
Date
Msg-id 8519.1403286102@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts  (Bruce Momjian <bruce@momjian.us>)
List pgsql-bugs
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> Bruce Momjian wrote:
>> Why would we want this if the system functions fine without those files
>> being created?  I don't think we want pg_resetxlog to be doing anything
>> except changing pg_controldata.

> I don't understand why you say the system functions fine.  If you move
> the multixactid with pg_resetxlog to a point which doesn't have the
> necessary file and page, the system will not start.  Only pg_upgrade
> knows to create the file appropriately, but normal operation doesn't.

Yeah.  In my mind, at least, there's been a TODO for some time for
pg_resetxlog to make sure that pg_clog and the other SLRU-like files
get populated appropriately when you tell it to change those counters.
You have to have a segment file at the right place or startup fails.

I'm not sure why Alvaro chose to fix this only for pg_multixact, but
fixing that case is better than not fixing anything.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts
Next
From: Pavan Deolasee
Date:
Subject: Re: BUG #10675: alter database set tablespace and unlogged table