1999-09-27 17:48:12 +02:00
|
|
|
/*
|
|
|
|
* rmgr.h
|
|
|
|
*
|
2000-10-21 17:43:36 +02:00
|
|
|
* Resource managers definition
|
1999-09-27 17:48:12 +02:00
|
|
|
*
|
2010-09-20 22:08:53 +02:00
|
|
|
* src/include/access/rmgr.h
|
1999-09-27 17:48:12 +02:00
|
|
|
*/
|
|
|
|
#ifndef RMGR_H
|
|
|
|
#define RMGR_H
|
|
|
|
|
2000-04-12 19:17:23 +02:00
|
|
|
typedef uint8 RmgrId;
|
1999-09-27 17:48:12 +02:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Built-in resource managers
|
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
|
|
|
*
|
2013-02-05 21:21:29 +01:00
|
|
|
* The actual numerical values for each rmgr ID are defined by the order
|
|
|
|
* of entries in rmgrlist.h.
|
|
|
|
*
|
|
|
|
* Note: RM_MAX_ID must fit in RmgrId; widening that type will affect the XLOG
|
|
|
|
* file format.
|
1999-09-27 17:48:12 +02:00
|
|
|
*/
|
2017-02-08 21:45:30 +01:00
|
|
|
#define PG_RMGR(symname,name,redo,desc,identify,startup,cleanup,mask) \
|
2013-02-05 21:21:29 +01:00
|
|
|
symname,
|
|
|
|
|
|
|
|
typedef enum RmgrIds
|
|
|
|
{
|
|
|
|
#include "access/rmgrlist.h"
|
|
|
|
RM_NEXT_ID
|
2014-05-06 18:12:18 +02:00
|
|
|
} RmgrIds;
|
2013-02-05 21:21:29 +01:00
|
|
|
|
|
|
|
#undef PG_RMGR
|
2011-12-17 22:41:16 +01:00
|
|
|
|
2013-02-05 21:21:29 +01:00
|
|
|
#define RM_MAX_ID (RM_NEXT_ID - 1)
|
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 /* RMGR_H */
|