X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id EEF19D1BA99 for ; Thu, 4 Sep 2003 14:26:58 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 39231-07 for ; Thu, 4 Sep 2003 11:26:52 -0300 (ADT) Received: from jais.jouy.inra.fr (jais.jouy.inra.fr [138.102.1.17]) by svr1.postgresql.org (Postfix) with ESMTP id 661D9D1BAA1 for ; Thu, 4 Sep 2003 11:26:47 -0300 (ADT) Received: from diamant.jouy.inra.fr (localhost [127.0.0.1]) by jais.jouy.inra.fr (8.10.1/8.10.1) with ESMTP id h84EQnV05864 for ; Thu, 4 Sep 2003 16:26:50 +0200 (MET DST) Received: from pc502jlo (pc502ljo [138.102.3.71]) by diamant.jouy.inra.fr (8.10.1/8.10.1) with SMTP id h84EQna15160 for ; Thu, 4 Sep 2003 16:26:49 +0200 (MET DST) Message-ID: <007c01c372f0$95b80b10$4703668a@pc502jlo> From: "Jouneau Luc" To: Subject: max_fsm_pages Date: Thu, 4 Sep 2003 16:26:46 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0079_01C37301.55CC4DC0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.1 tagged_above=0.0 required=5.0 tests=BAYES_30, HTML_50_60, RCVD_IN_OSIRUSOFT_COM X-Spam-Level: X-Archive-Number: 200309/74 X-Sequence-Number: 10162 This is a multi-part message in MIME format. ------=_NextPart_000_0079_01C37301.55CC4DC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi everybody, I'm trying to understand how vacuumdb and free space map work together for = retrieving free spaces after delete or update statements. max_fsm_pages and max_fsm_relations are set to default values (respectively= 10000 and 100). I do my tests on a table containing at the beginning 1931968 tuples stocked= in 11944 pages : INFO: Pages 11944: Changed 11944, Empty 0; Tup 1931968: Vac 0, Keep 0, UnU= sed 0 I delete 1931936 tuples (letting 32 tuples left). I thought the number of pages affected by this delete will overflow fsm sto= rage capacity, but when I run a vacuumdb verbose analyze on this table, I have the following log information : INFO: Removed 1397914 tuples in 8641 pages. CPU 0.76s/0.89u sec elapsed 25.72 sec. INFO: Removed 534022 tuples in 3303 pages. CPU 0.37s/0.29u sec elapsed 7.62 sec. INFO: Pages 11944: Changed 11944, Empty 0; Tup 32: Vac 1931936, Keep 0, Un= Used 0. Total CPU 1.57s/1.90u sec elapsed 42.01 sec. It seems that FSM traced all of my deletes since it mentions removes in 864= 1+3303=3D11944 pages (>10000 which was set for max_fsm_page). Can someone explain me, where I'm wrong ? My first aim was to know if max_fsm_pages was set for each table or for a w= hole database. Per table I suppose, but Is it a good supposition ? Where is stored (on disk) this fsm ? Thanks for your answers. Luc ------=_NextPart_000_0079_01C37301.55CC4DC0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi everybody,
 
I'm trying to understand how vacuumdb and = free=20 space map work together for retrieving free spaces after delete or update= =20 statements.
max_fsm_pages and max_fsm_relations= =20 are set to default values (respectively 10000 and 100).
I do my tests on a table containing at the= =20 beginning 1931968 tuples stocked in 11944 pages :

INFO:  Pages 11944: Changed 11944, Empty= 0; Tup=20 1931968: Vac 0, Keep 0, UnUsed 0

I delete 1931936 tuples (letting 32 tuples= =20 left).
I thought the number of pages affecte= d by this=20 delete will overflow fsm storage capacity, but when I run a vacuumdb verbos= e=20 analyze on this table,
I have the following log information :

INFO:  Removed 1397914 tuples in 8641=20 pages.

        CPU=20 0.76s/0.89u sec elapsed 25.72 sec.

INFO:  Removed 534022 tuples in 3303=20 pages.

        CPU=20 0.37s/0.29u sec elapsed 7.62 sec.

INFO:  Pages 11944: Changed 11944, Empty= 0; Tup=20 32: Vac 1931936, Keep 0, UnUsed 0.

       =20 Total CPU 1.57s/1.90u sec elapsed 42.01 sec.

It seems that FSM traced all of my deletes= since it=20 mentions removes in 8641+3303=3D11944 pages (>10000 which was set for=20 max_fsm_page).
 
Can someone explain me, where I'm wrong=20 ?
 
My first aim was to know if max_fsm_pages was set for each table or for a whole= =20 database. Per table I suppose, but Is it a good supposition ?
Where is stored (on disk) this fsm ?
 
Thanks for your answers.
 
Luc
------=_NextPart_000_0079_01C37301.55CC4DC0--