vacuum & free space map

From: Luca Ferrari <fluca1978(at)gmail(dot)com>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: vacuum & free space map
Date: 2019-08-06 08:13:35
Message-ID: CAKoxK+6iw0=Oz018jEJhTb2UNhFPcvP6Ckh-P+v0mTw4zXuR2w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Shital A 2019-08-06 08:14:59 Re: Compression In Postgresql 9.6
Previous Message Luca Ferrari 2019-08-06 07:20:33 Re: Does pgadmin4 work with postgresql 8.4?