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

From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: pgsql-hackers(at)postgresql(dot)org, tgl(at)postgresql(dot)org
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Fix free space map to correctly track the total amount of FSM
Date: 2007-10-02 09:40:19
Message-ID: 20071002.184019.98144148.t-ishii@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Sorry for replying to very old message. But... it seems this was not
backported to 8.1 or earlier. If so, how one could determine
max_fsm_pages is sufficient or not if he is running 8.1 or earlier?
--
Tatsuo Ishii
SRA OSS, Inc. Japan

> Log Message:
> -----------
> Fix free space map to correctly track the total amount of FSM space needed
> even when a single relation requires more than max_fsm_pages pages. Also,
> make VACUUM emit a warning in this case, since it likely means that VACUUM
> FULL or other drastic corrective measure is needed. Per reports from Jeff
> Frost and others of unexpected changes in the claimed max_fsm_pages need.
>
> Modified Files:
> --------------
> pgsql/contrib/pg_freespacemap:
> README.pg_freespacemap (r1.4 -> r1.5)
> (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pg_freespacemap/README.pg_freespacemap.diff?r1=1.4&r2=1.5)
> pg_freespacemap.c (r1.6 -> r1.7)
> (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pg_freespacemap/pg_freespacemap.c.diff?r1=1.6&r2=1.7)
> pg_freespacemap.sql.in (r1.5 -> r1.6)
> (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pg_freespacemap/pg_freespacemap.sql.in.diff?r1=1.5&r2=1.6)
> pgsql/src/backend/access/gin:
> ginvacuum.c (r1.5 -> r1.6)
> (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gin/ginvacuum.c.diff?r1=1.5&r2=1.6)
> pgsql/src/backend/access/gist:
> gistvacuum.c (r1.26 -> r1.27)
> (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gist/gistvacuum.c.diff?r1=1.26&r2=1.27)
> pgsql/src/backend/access/nbtree:
> nbtree.c (r1.150 -> r1.151)
> (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtree.c.diff?r1=1.150&r2=1.151)
> pgsql/src/backend/commands:
> vacuum.c (r1.339 -> r1.340)
> (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuum.c.diff?r1=1.339&r2=1.340)
> vacuumlazy.c (r1.78 -> r1.79)
> (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuumlazy.c.diff?r1=1.78&r2=1.79)
> pgsql/src/backend/storage/freespace:
> freespace.c (r1.54 -> r1.55)
> (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/freespace/freespace.c.diff?r1=1.54&r2=1.55)
> pgsql/src/include/storage:
> freespace.h (r1.21 -> r1.22)
> (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/storage/freespace.h.diff?r1=1.21&r2=1.22)
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Meskes 2007-10-02 09:50:00 pgsql: ITAGAKI Takahiro <itagaki.takahiro@oss.ntt.co.jp> added
Previous Message Magnus Hagander 2007-10-02 09:18:23 Re: [COMMITTERS] pgsql: Use BIO functions to avoid passing FILE * pointers to OpenSSL

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Meskes 2007-10-02 09:50:00 pgsql: ITAGAKI Takahiro <itagaki.takahiro@oss.ntt.co.jp> added
Previous Message Michael Paesold 2007-10-02 09:23:12 Re: First steps with 8.3 and autovacuum launcher