PG_FILEDUMP(1) User Commands PG_FILEDUMP(1)NAME
manual page for pg_filedump
SYNOPSIS
pg_filedump [-abcdfhixy] [-R startblock [endblock]] [-S blocksize] file
DESCRIPTION
Display formatted contents of a PostgreSQL heap/index/control file.
The following options are valid for heap and index files:
-a Display absolute addresses when formatting (Block header information is always block relative)
-b Display binary block images within a range (Option will turn off all formatting options)
-d Display formatted block content dump (Option will turn off all other formatting options)
-f Display formatted block content dump along with interpretation
-h Display this information
-i Display interpreted item details
-R Display specific block ranges within the file (Blocks are indexed from 0)
[startblock]: block to start at [endblock]: block to end at
A startblock without an endblock will format the single block
-S Force block size to [blocksize]
-x Force interpreted formatting of block items as index items
-y Force interpreted formatting of block items as heap items
The following options are valid for control files:
-c Interpret the file listed as a control file
-f Display formatted content dump along with interpretation
-S Force block size to [blocksize]
OTHERS
This manual page was generated from pg_filedump help output (-h) by help2man(1).
REPORTING BUGS
Report bugs to <pgsql-bugs@postgresql.org>
pg_filedump 9.2.0 June 2013 PG_FILEDUMP(1)
Check Out this Related Man Page
xfs_bmap(8) System Manager's Manual xfs_bmap(8)NAME
xfs_bmap - print block mapping for an XFS file
SYNOPSIS
xfs_bmap [ -adlpv ] [ -n num_extents ] file
DESCRIPTION
xfs_bmap prints the map of disk blocks used by files in an XFS filesystem. The map lists each extent used by the file, as well as regions
in the file that do not have any corresponding blocks (holes). Each line of the listings takes the following form:
extent: [startoffset..endoffset]: startblock..endblock
Holes are marked by replacing the startblock..endblock with hole. All the file offsets and disk blocks are in units of 512-byte blocks, no
matter what the filesystem's block size is.
OPTIONS -a If this option is specified, information about the file's attribute fork is printed instead of the default data fork.
-d If portions of the file have been migrated offline by a DMAPI application, a DMAPI read event will be generated to bring those por-
tions back online before the disk block map is printed. However if the -d option is used, no DMAPI read event will be generated for
a DMAPI file and offline portions will be reported as holes.
-l If this option is used, then
<nblocks> blocks
will be appended to each line. nblocks is the length of the extent described on the line in units of 512-byte blocks.
This flag has no effect if the -v option is used.
-n num_extents
If this option is given, xfs_bmap obtains the extent list of the file in groups of num_extents extents. In the absence of -n,
xfs_bmap queries the system for the number of extents in the file and uses that value to compute the group size.
-p If this option is used, xfs_bmap obtains all unwritten (preallocated) extents that do not contain written data. With the -v option,
the flags column will show which extents are preallocated/unwritten.
-v Shows verbose information. When this flag is specified, additional AG specific information is appended to each line in the following
form:
agno (startagoffset..endagoffset) nblocks flags
A second -v option will print out the flags legend.
SEE ALSO xfs_fsr(8), xfs(5).
xfs_bmap(8)