database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-30 11:03:19 +03:00
Code Activity

Use fork names instead of numbers in the file names for additional

Browse Source 
relation forks. While the file names are not visible to users, for those
that do peek into the data directory, it's nice to have more descriptive
names. Per Greg Stark's suggestion.
This commit is contained in:
Heikki Linnakangas
2008-10-06 14:13:17 +00:00
parent e59ad5fbb6
commit 5f853c6556
9 changed files with 67 additions and 64 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
doc/src/sgml/pageinspect.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/pageinspect.sgml,v 1.4 2008/09/30 10:52:09 heikki Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/pageinspect.sgml,v 1.5 2008/10/06 14:13:17 heikki Exp $ -->
<sect1 id="pageinspect">
<title>pageinspect</title>
@ -19,7 +19,7 @@
<variablelist>
<varlistentry>
<term>
<function>get_raw_page(relname text, forknum int, blkno int) returns bytea</function>
<function>get_raw_page(relname text, fork text, blkno int) returns bytea</function>
</term>
<listitem>
@ -27,8 +27,8 @@
<function>get_raw_page</function> reads the specified block of the named
table and returns a copy as a <type>bytea</> value. This allows a
single time-consistent copy of the block to be obtained.
<literal>forknum</literal> should be 0 for the main data fork, or 1 for
the FSM.
<literal>fork</literal> should be <literal>'main'</literal> for the main
data fork, or <literal>'fsm'</literal> for the FSM.
</para>
</listitem>
</varlistentry>

9
doc/src/sgml/storage.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/storage.sgml,v 1.25 2008/09/30 10:52:10 heikki Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/storage.sgml,v 1.26 2008/10/06 14:13:17 heikki Exp $ -->
<chapter id="storage">
@ -134,8 +134,7 @@ or index's <firstterm>filenode</> number, which can be found in
main file (aka. main fork), a <firstterm>free space map</> (see
<xref linkend="storage-fsm">) that stores information about free space
available in the relation, is stored in a file named after the filenode
number, with the the _1 suffix. For example, if the table's filenode number
is 12345, the FSM file is named <filename>12345_1</>.
number, with the the <literal>_fsm</> suffix.
</para>
<caution>
@ -385,9 +384,9 @@ comparison table, in which all the HTML pages were cut down to 7 kB to fit.
A Free Space Map is stored with every heap and index relation, except for
hash indexes, to keep track of available space in the relation. It's stored
along the main relation data, in a separate FSM relation fork, named after
relfilenode of the relation, but with a <literal>_1</> suffix. For example,
relfilenode of the relation, but with a <literal>_fsm</> suffix. For example,
if the relfilenode of a relation is 12345, the FSM is stored in a file called
<filename>12345_1</>, in the same directory as the main relation file.
<filename>12345_fsm</>, in the same directory as the main relation file.
</para>
<para>