Re: Prototype: In-place upgrade v02 - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Prototype: In-place upgrade v02
Date
Msg-id 48C4EC0C.2090400@enterprisedb.com
Whole thread Raw
In response to Re: Prototype: In-place upgrade v02  (Zdenek Kotala <Zdenek.Kotala@Sun.COM>)
Responses Re: Prototype: In-place upgrade v02  (Zdenek Kotala <Zdenek.Kotala@Sun.COM>)
List pgsql-hackers
Zdenek Kotala wrote:
> Heikki Linnakangas napsal(a):
>> Relation forks didn't change anything inside relation files, so no 
>> scanning of relations is required because of that. Neither will the 
>> FSM rewrite. Not sure about DSM yet.
> 
> Does it mean, that if you "inject" old data file after catalog upgrade, 
> then FSM will works without any problem?

Yes. You'll need to construct an FSM, but it doesn't necessarily need to 
reflect the reality. You could just fill it with zeros, meaning that 
there's no free space anywhere, and let the next vacuum fill it with 
real information. Or you could read the old pg_fsm.cache file and fill 
the new FSM accordingly.

> PS: I plan to review FSM this week.

Thanks!

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: ITAGAKI Takahiro
Date:
Subject: Re: [Review] pgbench duration option
Next
From: Heikki Linnakangas
Date:
Subject: Re: Prototype: In-place upgrade v02