diff --git a/contrib/pg_xlogdump/pg_xlogdump.c b/contrib/pg_xlogdump/pg_xlogdump.c index adc9087a1d..7f151f961c 100644 --- a/contrib/pg_xlogdump/pg_xlogdump.c +++ b/contrib/pg_xlogdump/pg_xlogdump.c @@ -15,8 +15,8 @@ #include #include -#include "access/xlog.h" #include "access/xlogreader.h" +#include "access/xlogrecord.h" #include "access/transam.h" #include "common/fe_memutils.h" #include "getopt_long.h" diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml index 0420610a01..6172a087f2 100644 --- a/doc/src/sgml/wal.sgml +++ b/doc/src/sgml/wal.sgml @@ -578,12 +578,12 @@ There are two commonly used internal WAL functions: - XLogInsert and XLogFlush. - XLogInsert is used to place a new record into + XLogInsertRecord and XLogFlush. + XLogInsertRecord is used to place a new record into the WAL buffers in shared memory. If there is no - space for the new record, XLogInsert will have + space for the new record, XLogInsertRecord will have to write (move to kernel cache) a few filled WAL - buffers. This is undesirable because XLogInsert + buffers. This is undesirable because XLogInsertRecord is used on every database low level modification (for example, row insertion) at a time when an exclusive lock is held on affected data pages, so the operation needs to be as fast as possible. What @@ -594,7 +594,7 @@ made, for the most part, at transaction commit time to ensure that transaction records are flushed to permanent storage. On systems with high log output, XLogFlush requests might - not occur often enough to prevent XLogInsert + not occur often enough to prevent XLogInsertRecord from having to do writes. On such systems one should increase the number of WAL buffers by modifying the parameter. When @@ -683,7 +683,7 @@ Enabling the configuration parameter (provided that PostgreSQL has been compiled with support for it) will result in each - XLogInsert and XLogFlush + XLogInsertRecord and XLogFlush WAL call being logged to the server log. This option might be replaced by a more general mechanism in the future. @@ -708,7 +708,7 @@ building the server). Each segment is divided into pages, normally 8 kB each (this size can be changed via the