2015-03-23 18:47:52 +01:00
|
|
|
/*-------------------------------------------------------------------------
|
|
|
|
*
|
|
|
|
* pg_rewind.h
|
|
|
|
*
|
|
|
|
*
|
2019-01-02 18:44:25 +01:00
|
|
|
* Portions Copyright (c) 1996-2019, PostgreSQL Global Development Group
|
2015-03-23 18:47:52 +01:00
|
|
|
* Portions Copyright (c) 1994, Regents of the University of California
|
|
|
|
*
|
|
|
|
*-------------------------------------------------------------------------
|
|
|
|
*/
|
|
|
|
#ifndef PG_REWIND_H
|
|
|
|
#define PG_REWIND_H
|
|
|
|
|
|
|
|
#include "datapagemap.h"
|
|
|
|
|
|
|
|
#include "access/timeline.h"
|
|
|
|
#include "storage/block.h"
|
|
|
|
#include "storage/relfilenode.h"
|
|
|
|
|
2019-05-14 20:19:49 +02:00
|
|
|
#include "common/logging.h"
|
2019-05-14 19:11:23 +02:00
|
|
|
|
2015-03-23 18:47:52 +01:00
|
|
|
/* Configuration options */
|
|
|
|
extern char *datadir_target;
|
|
|
|
extern char *datadir_source;
|
|
|
|
extern char *connstr_source;
|
|
|
|
extern bool showprogress;
|
|
|
|
extern bool dry_run;
|
Make WAL segment size configurable at initdb time.
For performance reasons a larger segment size than the default 16MB
can be useful. A larger segment size has two main benefits: Firstly,
in setups using archiving, it makes it easier to write scripts that
can keep up with higher amounts of WAL, secondly, the WAL has to be
written and synced to disk less frequently.
But at the same time large segment size are disadvantageous for
smaller databases. So far the segment size had to be configured at
compile time, often making it unrealistic to choose one fitting to a
particularly load. Therefore change it to a initdb time setting.
This includes a breaking changes to the xlogreader.h API, which now
requires the current segment size to be configured. For that and
similar reasons a number of binaries had to be taught how to recognize
the current segment size.
Author: Beena Emerson, editorialized by Andres Freund
Reviewed-By: Andres Freund, David Steele, Kuntal Ghosh, Michael
Paquier, Peter Eisentraut, Robert Hass, Tushar Ahuja
Discussion: https://postgr.es/m/CAOG9ApEAcQ--1ieKbhFzXSQPw_YLmepaa4hNdnY5+ZULpt81Mw@mail.gmail.com
2017-09-20 07:03:48 +02:00
|
|
|
extern int WalSegSz;
|
2015-03-23 18:47:52 +01:00
|
|
|
|
2015-12-01 16:56:44 +01:00
|
|
|
/* Target history */
|
|
|
|
extern TimeLineHistoryEntry *targetHistory;
|
2016-06-10 00:02:36 +02:00
|
|
|
extern int targetNentries;
|
2015-12-01 16:56:44 +01:00
|
|
|
|
2019-05-14 19:11:23 +02:00
|
|
|
/* Progress counters */
|
|
|
|
extern uint64 fetch_size;
|
|
|
|
extern uint64 fetch_done;
|
|
|
|
|
|
|
|
/* logging support */
|
|
|
|
#define pg_fatal(...) do { pg_log_fatal(__VA_ARGS__); exit(1); } while(0)
|
|
|
|
|
2015-03-23 18:47:52 +01:00
|
|
|
/* in parsexlog.c */
|
|
|
|
extern void extractPageMap(const char *datadir, XLogRecPtr startpoint,
|
2015-12-01 16:56:44 +01:00
|
|
|
int tliIndex, XLogRecPtr endpoint);
|
2015-03-23 18:47:52 +01:00
|
|
|
extern void findLastCheckpoint(const char *datadir, XLogRecPtr searchptr,
|
2015-12-01 16:56:44 +01:00
|
|
|
int tliIndex,
|
2015-03-23 18:47:52 +01:00
|
|
|
XLogRecPtr *lastchkptrec, TimeLineID *lastchkpttli,
|
|
|
|
XLogRecPtr *lastchkptredo);
|
|
|
|
extern XLogRecPtr readOneRecord(const char *datadir, XLogRecPtr ptr,
|
2015-12-01 16:56:44 +01:00
|
|
|
int tliIndex);
|
2015-03-23 18:47:52 +01:00
|
|
|
|
2019-05-14 19:11:23 +02:00
|
|
|
/* in pg_rewind.c */
|
|
|
|
extern void progress_report(bool force);
|
|
|
|
|
2015-03-23 18:47:52 +01:00
|
|
|
/* in timeline.c */
|
|
|
|
extern TimeLineHistoryEntry *rewind_parseTimeLineHistory(char *buffer,
|
|
|
|
TimeLineID targetTLI, int *nentries);
|
|
|
|
|
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 /* PG_REWIND_H */
|