Re: pg_freespacemap question

From: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
To: markir(at)paradise(dot)net(dot)nz
Cc: ishii(at)sraoss(dot)co(dot)jp, alvherre(at)commandprompt(dot)com, peter_e(at)gmx(dot)net, pgsql-hackers(at)postgresql(dot)org, tgl(at)sss(dot)pgh(dot)pa(dot)us
Subject: Re: pg_freespacemap question
Date: 2006-03-07 23:42:13
Message-ID: 20060308.084213.74728113.t-ishii@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

> > BTW, I found the answer to my question myself by reading the source
> > code: if that's an index, then blockfreebytes is explicitly set to 0.
> > I suggest that this should be noted in the README and in this case
> > blockfreebytes is better to set to NULL, rather than 0.
> >
>
> Good points! I had not noticed this test case. Probably NULL is better
> than zero.

Just for curiousity, why FSM gathers info for indexes? I thought FSM
is only good for tables.
--
Tatsuo Ishii
SRA OSS, Inc. Japan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2006-03-07 23:49:24 Re: pg_freespacemap question
Previous Message Mark Kirkwood 2006-03-07 23:31:36 Re: pg_freespacemap question

Browse pgsql-patches by date

  From Date Subject
Next Message Alvaro Herrera 2006-03-07 23:49:24 Re: pg_freespacemap question
Previous Message Mark Kirkwood 2006-03-07 23:31:36 Re: pg_freespacemap question