Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> This would only happen if a VACUUM FULL had been run on the pre-9.0
> database and it had failed part way through.
If that were true, you might have an argument, but it isn't. VACUUM
FULL was never very careful about getting rid of all MOVED_xxx bits.
See the comments for update_hint_bits().
> We should remove the moved in/off flag bits and make it a part of the
> upgrade process to ensure the absence of those states.
That's not happening. The whole point of upgrade in place is to not do
anything as expensive as a full-database scan.
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Alexey Klyukin||Date: 2010-02-11 16:10:30|
|Subject: a common place for pl/perlu modules|
|Previous:||From: Robert Haas||Date: 2010-02-11 15:53:22|
|Subject: Re: Writeable CTEs and empty relations|
pgsql-committers by date
|Next:||From: Tom Lane||Date: 2010-02-11 16:27:38|
|Subject: Re: Re: [COMMITTERS] pgsql: Remove old-style VACUUM FULL (which was known for a little while |
|Previous:||From: Euler Taveira de Oliveira||Date: 2010-02-11 15:29:38|
|Subject: Re: Re: [COMMITTERS] pgsql: Make standby server continuously
retry restoring the next WAL|