|
|
|
|
/*-------------------------------------------------------------------------
|
|
|
|
|
*
|
|
|
|
|
* filemap.h
|
|
|
|
|
*
|
|
|
|
|
* Copyright (c) 2013-2019, PostgreSQL Global Development Group
|
|
|
|
|
*-------------------------------------------------------------------------
|
|
|
|
|
*/
|
|
|
|
|
#ifndef FILEMAP_H
|
|
|
|
|
#define FILEMAP_H
|
|
|
|
|
|
|
|
|
|
#include "storage/relfilenode.h"
|
|
|
|
|
#include "storage/block.h"
|
|
|
|
|
|
|
|
|
|
#include "datapagemap.h"
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* For every file found in the local or remote system, we have a file entry
|
|
|
|
|
* which says what we are going to do with the file. For relation files,
|
|
|
|
|
* there is also a page map, marking pages in the file that were changed
|
|
|
|
|
* locally.
|
|
|
|
|
*
|
|
|
|
|
* The enum values are sorted in the order we want actions to be processed.
|
|
|
|
|
*/
|
|
|
|
|
typedef enum
|
|
|
|
|
{
|
|
|
|
|
FILE_ACTION_CREATE, /* create local directory or symbolic link */
|
|
|
|
|
FILE_ACTION_COPY, /* copy whole file, overwriting if exists */
|
|
|
|
|
FILE_ACTION_COPY_TAIL, /* copy tail from 'oldsize' to 'newsize' */
|
|
|
|
|
FILE_ACTION_NONE, /* no action (we might still copy modified
|
|
|
|
|
* blocks based on the parsed WAL) */
|
|
|
|
|
FILE_ACTION_TRUNCATE, /* truncate local file to 'newsize' bytes */
|
|
|
|
|
FILE_ACTION_REMOVE /* remove local file / directory / symlink */
|
|
|
|
|
} file_action_t;
|
|
|
|
|
|
|
|
|
|
typedef enum
|
|
|
|
|
{
|
|
|
|
|
FILE_TYPE_REGULAR,
|
|
|
|
|
FILE_TYPE_DIRECTORY,
|
|
|
|
|
FILE_TYPE_SYMLINK
|
|
|
|
|
} file_type_t;
|
|
|
|
|
|
|
|
|
|
typedef struct file_entry_t
|
|
|
|
|
{
|
|
|
|
|
char *path;
|
|
|
|
|
file_type_t type;
|
|
|
|
|
|
|
|
|
|
file_action_t action;
|
|
|
|
|
|
|
|
|
|
/* for a regular file */
|
|
|
|
|
size_t oldsize;
|
|
|
|
|
size_t newsize;
|
|
|
|
|
bool isrelfile; /* is it a relation data file? */
|
|
|
|
|
|
|
|
|
|
datapagemap_t pagemap;
|
|
|
|
|
|
|
|
|
|
/* for a symlink */
|
|
|
|
|
char *link_target;
|
|
|
|
|
|
|
|
|
|
struct file_entry_t *next;
|
|
|
|
|
} file_entry_t;
|
|
|
|
|
|
|
|
|
|
typedef struct filemap_t
|
|
|
|
|
{
|
|
|
|
|
/*
|
|
|
|
|
* New entries are accumulated to a linked list, in process_source_file
|
|
|
|
|
* and process_target_file.
|
|
|
|
|
*/
|
|
|
|
|
file_entry_t *first;
|
|
|
|
|
file_entry_t *last;
|
|
|
|
|
int nlist; /* number of entries currently in list */
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* After processing all the remote files, the entries in the linked list
|
|
|
|
|
* are moved to this array. After processing local files, too, all the
|
|
|
|
|
* local entries are added to the array by filemap_finalize, and sorted in
|
|
|
|
|
* the final order. After filemap_finalize, all the entries are in the
|
|
|
|
|
* array, and the linked list is empty.
|
|
|
|
|
*/
|
|
|
|
|
file_entry_t **array;
|
|
|
|
|
int narray; /* current length of array */
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Summary information. total_size is the total size of the source
|
|
|
|
|
* cluster, and fetch_size is the number of bytes that needs to be copied.
|
|
|
|
|
*/
|
|
|
|
|
uint64 total_size;
|
|
|
|
|
uint64 fetch_size;
|
|
|
|
|
} filemap_t;
|
|
|
|
|
|
|
|
|
|
extern filemap_t *filemap;
|
|
|
|
|
|
|
|
|
|
extern void filemap_create(void);
|
|
|
|
|
extern void calculate_totals(void);
|
|
|
|
|
extern void print_filemap(void);
|
|
|
|
|
|
|
|
|
|
/* Functions for populating the filemap */
|
|
|
|
|
extern void process_source_file(const char *path, file_type_t type,
|
|
|
|
|
size_t newsize, const char *link_target);
|
|
|
|
|
extern void process_target_file(const char *path, file_type_t type,
|
|
|
|
|
size_t newsize, const char *link_target);
|
|
|
|
|
extern void process_block_change(ForkNumber forknum, RelFileNode rnode,
|
|
|
|
|
BlockNumber blkno);
|
|
|
|
|
extern void filemap_finalize(void);
|
|
|
|
|
|
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
9 years ago
|
|
|
#endif /* FILEMAP_H */
|