2001-08-25 20:52:43 +02:00
|
|
|
/*
|
|
|
|
* clog.h
|
|
|
|
*
|
|
|
|
* PostgreSQL transaction-commit-log manager
|
|
|
|
*
|
2019-01-02 18:44:25 +01:00
|
|
|
* Portions Copyright (c) 1996-2019, PostgreSQL Global Development Group
|
2001-08-25 20:52:43 +02:00
|
|
|
* Portions Copyright (c) 1994, Regents of the University of California
|
|
|
|
*
|
2010-09-20 22:08:53 +02:00
|
|
|
* src/include/access/clog.h
|
2001-08-25 20:52:43 +02:00
|
|
|
*/
|
|
|
|
#ifndef CLOG_H
|
|
|
|
#define CLOG_H
|
|
|
|
|
Revamp the WAL record format.
Each WAL record now carries information about the modified relation and
block(s) in a standardized format. That makes it easier to write tools that
need that information, like pg_rewind, prefetching the blocks to speed up
recovery, etc.
There's a whole new API for building WAL records, replacing the XLogRecData
chains used previously. The new API consists of XLogRegister* functions,
which are called for each buffer and chunk of data that is added to the
record. The new API also gives more control over when a full-page image is
written, by passing flags to the XLogRegisterBuffer function.
This also simplifies the XLogReadBufferForRedo() calls. The function can dig
the relation and block number from the WAL record, so they no longer need to
be passed as arguments.
For the convenience of redo routines, XLogReader now disects each WAL record
after reading it, copying the main data part and the per-block data into
MAXALIGNed buffers. The data chunks are not aligned within the WAL record,
but the redo routines can assume that the pointers returned by XLogRecGet*
functions are. Redo routines are now passed the XLogReaderState, which
contains the record in the already-disected format, instead of the plain
XLogRecord.
The new record format also makes the fixed size XLogRecord header smaller,
by removing the xl_len field. The length of the "main data" portion is now
stored at the end of the WAL record, and there's a separate header after
XLogRecord for it. The alignment padding at the end of XLogRecord is also
removed. This compansates for the fact that the new format would otherwise
be more bulky than the old format.
Reviewed by Andres Freund, Amit Kapila, Michael Paquier, Alvaro Herrera,
Fujii Masao.
2014-11-20 16:56:26 +01:00
|
|
|
#include "access/xlogreader.h"
|
2014-11-06 12:52:08 +01:00
|
|
|
#include "lib/stringinfo.h"
|
2001-08-25 20:52:43 +02:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Possible transaction statuses --- note that all-zeroes is the initial
|
|
|
|
* state.
|
2004-07-01 02:52:04 +02:00
|
|
|
*
|
|
|
|
* A "subcommitted" transaction is a committed subtransaction whose parent
|
|
|
|
* hasn't committed or aborted yet.
|
2001-08-25 20:52:43 +02:00
|
|
|
*/
|
|
|
|
typedef int XidStatus;
|
|
|
|
|
|
|
|
#define TRANSACTION_STATUS_IN_PROGRESS 0x00
|
|
|
|
#define TRANSACTION_STATUS_COMMITTED 0x01
|
|
|
|
#define TRANSACTION_STATUS_ABORTED 0x02
|
2004-07-01 02:52:04 +02:00
|
|
|
#define TRANSACTION_STATUS_SUB_COMMITTED 0x03
|
2001-08-25 20:52:43 +02:00
|
|
|
|
2017-03-23 19:08:23 +01:00
|
|
|
typedef struct xl_clog_truncate
|
|
|
|
{
|
2017-05-17 22:31:56 +02:00
|
|
|
int pageno;
|
2017-03-23 19:08:23 +01:00
|
|
|
TransactionId oldestXact;
|
2017-05-17 22:31:56 +02:00
|
|
|
Oid oldestXactDb;
|
2017-03-23 19:08:23 +01:00
|
|
|
} xl_clog_truncate;
|
2001-08-25 20:52:43 +02:00
|
|
|
|
2009-06-11 16:49:15 +02:00
|
|
|
extern void TransactionIdSetTreeStatus(TransactionId xid, int nsubxids,
|
Phase 3 of pgindent updates.
Don't move parenthesized lines to the left, even if that means they
flow past the right margin.
By default, BSD indent lines up statement continuation lines that are
within parentheses so that they start just to the right of the preceding
left parenthesis. However, traditionally, if that resulted in the
continuation line extending to the right of the desired right margin,
then indent would push it left just far enough to not overrun the margin,
if it could do so without making the continuation line start to the left of
the current statement indent. That makes for a weird mix of indentations
unless one has been completely rigid about never violating the 80-column
limit.
This behavior has been pretty universally panned by Postgres developers.
Hence, disable it with indent's new -lpl switch, so that parenthesized
lines are always lined up with the preceding left paren.
This patch is much less interesting than the first round of indent
changes, but also bulkier, so I thought it best to separate the effects.
Discussion: https://postgr.es/m/E1dAmxK-0006EE-1r@gemulon.postgresql.org
Discussion: https://postgr.es/m/30527.1495162840@sss.pgh.pa.us
2017-06-21 21:35:54 +02:00
|
|
|
TransactionId *subxids, XidStatus status, XLogRecPtr lsn);
|
2007-08-02 00:45:09 +02:00
|
|
|
extern XidStatus TransactionIdGetStatus(TransactionId xid, XLogRecPtr *lsn);
|
2001-08-25 20:52:43 +02:00
|
|
|
|
2012-01-06 20:30:23 +01:00
|
|
|
extern Size CLOGShmemBuffers(void);
|
2005-08-21 01:26:37 +02:00
|
|
|
extern Size CLOGShmemSize(void);
|
2001-08-25 20:52:43 +02:00
|
|
|
extern void CLOGShmemInit(void);
|
|
|
|
extern void BootStrapCLOG(void);
|
|
|
|
extern void StartupCLOG(void);
|
2011-11-02 09:07:44 +01:00
|
|
|
extern void TrimCLOG(void);
|
2001-08-25 20:52:43 +02:00
|
|
|
extern void ShutdownCLOG(void);
|
|
|
|
extern void CheckPointCLOG(void);
|
|
|
|
extern void ExtendCLOG(TransactionId newestXact);
|
2017-03-23 19:08:23 +01:00
|
|
|
extern void TruncateCLOG(TransactionId oldestXact, Oid oldestxid_datoid);
|
2004-08-24 01:22:45 +02:00
|
|
|
|
|
|
|
/* XLOG stuff */
|
|
|
|
#define CLOG_ZEROPAGE 0x00
|
Fix recently-understood problems with handling of XID freezing, particularly
in PITR scenarios. We now WAL-log the replacement of old XIDs with
FrozenTransactionId, so that such replacement is guaranteed to propagate to
PITR slave databases. Also, rather than relying on hint-bit updates to be
preserved, pg_clog is not truncated until all instances of an XID are known to
have been replaced by FrozenTransactionId. Add new GUC variables and
pg_autovacuum columns to allow management of the freezing policy, so that
users can trade off the size of pg_clog against the amount of freezing work
done. Revise the already-existing code that forces autovacuum of tables
approaching the wraparound point to make it more bulletproof; also, revise the
autovacuum logic so that anti-wraparound vacuuming is done per-table rather
than per-database. initdb forced because of changes in pg_class, pg_database,
and pg_autovacuum catalogs. Heikki Linnakangas, Simon Riggs, and Tom Lane.
2006-11-05 23:42:10 +01:00
|
|
|
#define CLOG_TRUNCATE 0x10
|
2004-08-24 01:22:45 +02:00
|
|
|
|
Revamp the WAL record format.
Each WAL record now carries information about the modified relation and
block(s) in a standardized format. That makes it easier to write tools that
need that information, like pg_rewind, prefetching the blocks to speed up
recovery, etc.
There's a whole new API for building WAL records, replacing the XLogRecData
chains used previously. The new API consists of XLogRegister* functions,
which are called for each buffer and chunk of data that is added to the
record. The new API also gives more control over when a full-page image is
written, by passing flags to the XLogRegisterBuffer function.
This also simplifies the XLogReadBufferForRedo() calls. The function can dig
the relation and block number from the WAL record, so they no longer need to
be passed as arguments.
For the convenience of redo routines, XLogReader now disects each WAL record
after reading it, copying the main data part and the per-block data into
MAXALIGNed buffers. The data chunks are not aligned within the WAL record,
but the redo routines can assume that the pointers returned by XLogRecGet*
functions are. Redo routines are now passed the XLogReaderState, which
contains the record in the already-disected format, instead of the plain
XLogRecord.
The new record format also makes the fixed size XLogRecord header smaller,
by removing the xl_len field. The length of the "main data" portion is now
stored at the end of the WAL record, and there's a separate header after
XLogRecord for it. The alignment padding at the end of XLogRecord is also
removed. This compansates for the fact that the new format would otherwise
be more bulky than the old format.
Reviewed by Andres Freund, Amit Kapila, Michael Paquier, Alvaro Herrera,
Fujii Masao.
2014-11-20 16:56:26 +01:00
|
|
|
extern void clog_redo(XLogReaderState *record);
|
|
|
|
extern void clog_desc(StringInfo buf, XLogReaderState *record);
|
2014-09-19 15:17:12 +02:00
|
|
|
extern const char *clog_identify(uint8 info);
|
2001-10-28 07:26:15 +01:00
|
|
|
|
Phase 2 of pgindent updates.
Change pg_bsd_indent to follow upstream rules for placement of comments
to the right of code, and remove pgindent hack that caused comments
following #endif to not obey the general rule.
Commit e3860ffa4dd0dad0dd9eea4be9cc1412373a8c89 wasn't actually using
the published version of pg_bsd_indent, but a hacked-up version that
tried to minimize the amount of movement of comments to the right of
code. The situation of interest is where such a comment has to be
moved to the right of its default placement at column 33 because there's
code there. BSD indent has always moved right in units of tab stops
in such cases --- but in the previous incarnation, indent was working
in 8-space tab stops, while now it knows we use 4-space tabs. So the
net result is that in about half the cases, such comments are placed
one tab stop left of before. This is better all around: it leaves
more room on the line for comment text, and it means that in such
cases the comment uniformly starts at the next 4-space tab stop after
the code, rather than sometimes one and sometimes two tabs after.
Also, ensure that comments following #endif are indented the same
as comments following other preprocessor commands such as #else.
That inconsistency turns out to have been self-inflicted damage
from a poorly-thought-through post-indent "fixup" in pgindent.
This patch is much less interesting than the first round of indent
changes, but also bulkier, so I thought it best to separate the effects.
Discussion: https://postgr.es/m/E1dAmxK-0006EE-1r@gemulon.postgresql.org
Discussion: https://postgr.es/m/30527.1495162840@sss.pgh.pa.us
2017-06-21 21:18:54 +02:00
|
|
|
#endif /* CLOG_H */
|