aboutsummaryrefslogtreecommitdiff
path: root/doc/src/sgml/pgfreespacemap.sgml
blob: bc821ead6ba53a99c7f2b9648d976a30b2ccf799 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
<!-- $PostgreSQL: pgsql/doc/src/sgml/pgfreespacemap.sgml,v 2.2 2007/12/10 05:32:51 tgl Exp $ -->

<sect1 id="pgfreespacemap">
 <title>pg_freespacemap</title>

 <indexterm zone="pgfreespacemap">
  <primary>pg_freespacemap</primary>
 </indexterm>

 <para>
  The <filename>pg_freespacemap</> module provides a means for examining the
  free space map (FSM). It provides two C functions:
  <function>pg_freespacemap_relations</function> and
  <function>pg_freespacemap_pages</function> that each return a set of
  records, plus two views <structname>pg_freespacemap_relations</structname>
  and <structname>pg_freespacemap_pages</structname> that wrap the functions
  for convenient use.
 </para>

 <para>
  By default public access is revoked from the functions and views, just in
  case there are security issues lurking.
 </para>

 <sect2>
  <title>The <filename>pg_freespacemap</> views</title>

  <para>
   The definitions of the columns exposed by the views are:
  </para>

  <table>
   <title><structname>pg_freespacemap_relations</> Columns</title>

   <tgroup cols="4">
    <thead>
     <row>
      <entry>Name</entry>
      <entry>Type</entry>
      <entry>References</entry>
      <entry>Description</entry>
     </row>
    </thead>
    <tbody>

     <row>
      <entry><structfield>reltablespace</structfield></entry>
      <entry><type>oid</type></entry>
      <entry><literal>pg_tablespace.oid</literal></entry>
      <entry>Tablespace OID of the relation</entry>
     </row>
     <row>
      <entry><structfield>reldatabase</structfield></entry>
      <entry><type>oid</type></entry>
      <entry><literal>pg_database.oid</literal></entry>
      <entry>Database OID of the relation</entry>
     </row>
     <row>
      <entry><structfield>relfilenode</structfield></entry>
      <entry><type>oid</type></entry>
      <entry><literal>pg_class.relfilenode</literal></entry>
      <entry>Relfilenode of the relation</entry>
     </row>
     <row>
      <entry><structfield>avgrequest</structfield></entry>
      <entry><type>integer</type></entry>
      <entry></entry>
      <entry>Moving average of free space requests (NULL for indexes)</entry>
     </row>
     <row>
      <entry><structfield>interestingpages</structfield></entry>
      <entry><type>integer</type></entry>
      <entry></entry>
      <entry>Count of pages last reported as containing useful free space</entry>
     </row>
     <row>
      <entry><structfield>storedpages</structfield></entry>
      <entry><type>integer</type></entry>
      <entry></entry>
      <entry>Count of pages actually stored in free space map</entry>
     </row>
     <row>
      <entry><structfield>nextpage</structfield></entry>
      <entry><type>integer</type></entry>
      <entry></entry>
      <entry>Page index (from 0) to start next search at</entry>
     </row>

    </tbody>
   </tgroup>
  </table>

  <table>
   <title><structname>pg_freespacemap_pages</> Columns</title>

   <tgroup cols="4">
    <thead>
     <row>
      <entry>Name</entry>
      <entry>Type</entry>
      <entry>References</entry>
      <entry>Description</entry>
     </row>
    </thead>
    <tbody>

     <row>
      <entry><structfield>reltablespace</structfield></entry>
      <entry><type>oid</type></entry>
      <entry><literal>pg_tablespace.oid</literal></entry>
      <entry>Tablespace OID of the relation</entry>
     </row>
     <row>
      <entry><structfield>reldatabase</structfield></entry>
      <entry><type>oid</type></entry>
      <entry><literal>pg_database.oid</literal></entry>
      <entry>Database OID of the relation</entry>
     </row>
     <row>
      <entry><structfield>relfilenode</structfield></entry>
      <entry><type>oid</type></entry>
      <entry><literal>pg_class.relfilenode</literal></entry>
      <entry>Relfilenode of the relation</entry>
     </row>
     <row>
      <entry><structfield>relblocknumber</structfield></entry>
      <entry><type>bigint</type></entry>
      <entry></entry>
      <entry>Page number within the relation</entry>
     </row>
     <row>
      <entry><structfield>bytes</structfield></entry>
      <entry><type>integer</type></entry>
      <entry></entry>
      <entry>Free bytes in the page, or NULL for an index page (see below)</entry>
     </row>

    </tbody>
   </tgroup>
  </table>

  <para>
   For <structname>pg_freespacemap_relations</structname>, there is one row
   for each relation in the free space map.
   <structfield>storedpages</structfield> is the number of pages actually
   stored in the map, while <structfield>interestingpages</structfield> is the
   number of pages the last <command>VACUUM</> thought had useful amounts of
   free space.
  </para>

  <para>
   If <structfield>storedpages</structfield> is consistently less than
   <structfield>interestingpages</> then it'd be a good idea to increase
   <varname>max_fsm_pages</varname>.  Also, if the number of rows in
   <structname>pg_freespacemap_relations</structname> is close to
   <varname>max_fsm_relations</varname>, then you should consider increasing
   <varname>max_fsm_relations</varname>.
  </para>

  <para>
   For <structname>pg_freespacemap_pages</structname>, there is one row for
   each page in the free space map. The number of rows for a relation will
   match the <structfield>storedpages</structfield> column in
   <structname>pg_freespacemap_relations</structname>.
  </para>

  <para>
   For indexes, what is tracked is entirely-unused pages, rather than free
   space within pages.  Therefore, the average request size and free bytes
   within a page are not meaningful, and are shown as NULL.
  </para>

  <para>
   Because the map is shared by all the databases, there will normally be
   entries for relations not belonging to the current database.  This means
   that there may not be matching join rows in <structname>pg_class</> for
   some rows, or that there could even be incorrect joins.  If you are
   trying to join against <structname>pg_class</>, it's a good idea to
   restrict the join to rows having <structfield>reldatabase</> equal to
   the current database's OID or zero.
  </para>

  <para>
   When either of the views is accessed, internal free space map locks are
   taken for long enough to copy all the state data that the view will display.
   This ensures that the views produce a consistent set of results, while not
   blocking normal activity longer than necessary.  Nonetheless there
   could be some impact on database performance if they are read often.
  </para>
 </sect2>

 <sect2>
  <title>Sample output</title>

  <programlisting>
regression=# SELECT c.relname, r.avgrequest, r.interestingpages, r.storedpages
             FROM pg_freespacemap_relations r INNER JOIN pg_class c
             ON r.relfilenode = c.relfilenode AND
                r.reldatabase IN (0, (SELECT oid FROM pg_database
                                      WHERE datname = current_database()))
             ORDER BY r.storedpages DESC LIMIT 10;
             relname             | avgrequest | interestingpages | storedpages
---------------------------------+------------+------------------+-------------
 onek                            |        256 |              109 |         109
 pg_attribute                    |        167 |               93 |          93
 pg_class                        |        191 |               49 |          49
 pg_attribute_relid_attnam_index |            |               48 |          48
 onek2                           |        256 |               37 |          37
 pg_depend                       |         95 |               26 |          26
 pg_type                         |        199 |               16 |          16
 pg_rewrite                      |       1011 |               13 |          13
 pg_class_relname_nsp_index      |            |               10 |          10
 pg_proc                         |        302 |                8 |           8
(10 rows)

regression=# SELECT c.relname, p.relblocknumber, p.bytes
             FROM pg_freespacemap_pages p INNER JOIN pg_class c
             ON p.relfilenode = c.relfilenode AND
                p.reldatabase IN (0, (SELECT oid FROM pg_database
                                      WHERE datname = current_database()))
             ORDER BY c.relname LIMIT 10;
   relname    | relblocknumber | bytes
--------------+----------------+-------
 a_star       |              0 |  8040
 abstime_tbl  |              0 |  7908
 aggtest      |              0 |  8008
 altinhoid    |              0 |  8128
 altstartwith |              0 |  8128
 arrtest      |              0 |  7172
 b_star       |              0 |  7976
 box_tbl      |              0 |  7912
 bt_f8_heap   |             54 |  7728
 bt_i4_heap   |             49 |  8008
(10 rows)
  </programlisting>
 </sect2>

 <sect2>
  <title>Author</title>

  <para>
   Mark Kirkwood <email>markir@paradise.net.nz</email>
  </para>
 </sect2>

</sect1>