2004-07-19 04:47:16 +02:00
|
|
|
/*-------------------------------------------------------------------------
|
|
|
|
*
|
|
|
|
* pgarch.h
|
|
|
|
* Exports from postmaster/pgarch.c.
|
|
|
|
*
|
2019-01-02 18:44:25 +01:00
|
|
|
* Portions Copyright (c) 1996-2019, PostgreSQL Global Development Group
|
2004-07-19 04:47:16 +02:00
|
|
|
* Portions Copyright (c) 1994, Regents of the University of California
|
|
|
|
*
|
2010-09-20 22:08:53 +02:00
|
|
|
* src/include/postmaster/pgarch.h
|
2004-07-19 04:47:16 +02:00
|
|
|
*
|
|
|
|
*-------------------------------------------------------------------------
|
|
|
|
*/
|
|
|
|
#ifndef _PGARCH_H
|
|
|
|
#define _PGARCH_H
|
|
|
|
|
2014-01-28 18:58:22 +01:00
|
|
|
/* ----------
|
|
|
|
* Archiver control info.
|
|
|
|
*
|
2016-10-20 17:24:37 +02:00
|
|
|
* We expect that archivable files within pg_wal will have names between
|
2014-01-28 18:58:22 +01:00
|
|
|
* MIN_XFN_CHARS and MAX_XFN_CHARS in length, consisting only of characters
|
|
|
|
* appearing in VALID_XFN_CHARS. The status files in archive_status have
|
|
|
|
* corresponding names with ".ready" or ".done" appended.
|
|
|
|
* ----------
|
|
|
|
*/
|
|
|
|
#define MIN_XFN_CHARS 16
|
|
|
|
#define MAX_XFN_CHARS 40
|
At promotion, archive last segment from old timeline with .partial suffix.
Previously, we would archive the possible-incomplete WAL segment with its
normal filename, but that causes trouble if the server owning that timeline
is still running, and tries to archive the same segment later. It's not nice
for the standby to trip up the master's archival like that. And it's pretty
confusing, anyway, to have an incomplete segment in the archive that's
indistinguishable from a normal, complete segment.
To avoid such confusion, add a .partial suffix to the file. Or to be more
precise, make a copy of the old segment under the .partial suffix, and
archive that instead of the original file. pg_receivexlog also uses the
.partial suffix for the same purpose, to tell apart incompletely streamed
files from complete ones.
There is no automatic mechanism to use the .partial files at recovery, so
they will go unused, unless the administrator manually copies to them to
the pg_xlog directory (and removes the .partial suffix). Recovery won't
normally need the WAL - when recovering to the new timeline, it will find
the same WAL on the first segment on the new timeline instead - but it
nevertheless feels better to archive the file with the .partial suffix, for
debugging purposes if nothing else.
2015-05-08 20:59:01 +02:00
|
|
|
#define VALID_XFN_CHARS "0123456789ABCDEF.history.backup.partial"
|
2014-01-28 18:58:22 +01:00
|
|
|
|
2004-07-19 04:47:16 +02:00
|
|
|
/* ----------
|
|
|
|
* Functions called from postmaster
|
|
|
|
* ----------
|
|
|
|
*/
|
|
|
|
extern int pgarch_start(void);
|
|
|
|
|
|
|
|
#ifdef EXEC_BACKEND
|
2015-03-26 19:03:19 +01:00
|
|
|
extern void PgArchiverMain(int argc, char *argv[]) pg_attribute_noreturn();
|
2004-07-19 04:47:16 +02:00
|
|
|
#endif
|
|
|
|
|
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 /* _PGARCH_H */
|