vacuum & free space map - Mailing list pgsql-general

From Luca Ferrari
Subject vacuum & free space map
Date
Msg-id CAKoxK+6iw0=Oz018jEJhTb2UNhFPcvP6Ckh-P+v0mTw4zXuR2w@mail.gmail.com
Whole thread Raw
Responses Re: vacuum & free space map  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Hi,
I'm not understanding why a vacuum full clears a FSM information while
a normal vacuum does not. On a table with fillfactor = 50 I've got:

testdb=> vacuum full respi.pull_status;
VACUUM
testdb=> SELECT * FROM pg_freespace( 'respi.pull_status', 0 );
 pg_freespace
--------------
            0
(1 row)

testdb=> vacuum respi.pull_status;
VACUUM
testdb=> SELECT * FROM pg_freespace( 'respi.pull_status', 0 );
 pg_freespace
--------------
         4096
(1 row)

So why is vacuum full not considering the fillfactor and clearing the
FSM? Or am I misunderstanding the results from pg_freespace?
This is on postgresql 11.4.

Thanks,
Luca



pgsql-general by date:

Previous
From: Luca Ferrari
Date:
Subject: Re: Does pgadmin4 work with postgresql 8.4?
Next
From: Shital A
Date:
Subject: Re: Compression In Postgresql 9.6