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

From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: pgsql-hackers(at)postgresql(dot)org, pgsql-committers(at)postgresql(dot)org
Subject: Re: [HACKERS] Re: pgsql: Fix free space map to correctly track the total amount of FSM
Date: 2007-10-02 15:37:36
Message-ID: 20071003.003736.74407817.t-ishii@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

> Tatsuo Ishii <ishii(at)postgresql(dot)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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Magnus Hagander 2007-10-02 19:01:45 pgsql: Default to thread safety on, and support more CPU options.
Previous Message Tom Lane 2007-10-02 15:22:47 Re: [HACKERS] Re: pgsql: Fix free space map to correctly track the total amount of FSM

Browse pgsql-hackers by date

  From Date Subject
Next Message ஆமாச்சு 2007-10-02 16:02:46 Re: Beginning Tamil Community for Postgre
Previous Message Tom Lane 2007-10-02 15:22:47 Re: [HACKERS] Re: pgsql: Fix free space map to correctly track the total amount of FSM