Re: [HACKERS] Re: pgsql: Fix free space map to correctly track the total amount of FSM - Mailing list pgsql-committers

From Tatsuo Ishii
Subject Re: [HACKERS] Re: pgsql: Fix free space map to correctly track the total amount of FSM
Date
Msg-id 20071003.003736.74407817.t-ishii@sraoss.co.jp
Whole thread Raw
In response to Re: [HACKERS] Re: pgsql: Fix free space map to correctly track the total amount of FSM  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] Re: pgsql: Fix free space map to correctly track the total amount of FSM  (Decibel! <decibel@decibel.org>)
List pgsql-committers
> Tatsuo Ishii <ishii@postgresql.org> writes:
> > Sorry for replying to very old message. But... it seems this was not
> > backported to 8.1 or earlier.
>
> Since it involved a change in the FSM API, it didn't seem reasonable
> to back-patch it.

So for those versions of PostgreSQL the only way to know the
appropriate FSM pages is change FSM-restart postmaster-do vacuum cycle
until vacuum reports the same number of "total page needed"?
--
Tatsuo Ishii
SRA OSS, Inc. Japan

pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Re: pgsql: Fix free space map to correctly track the total amount of FSM
Next
From: mha@postgresql.org (Magnus Hagander)
Date:
Subject: pgsql: Default to thread safety on, and support more CPU options.