name:Build Probackup

on:

push:

branches:

-"**"

workflow_dispatch:

jobs:

build-win2019:

runs-on:

-windows-2019

env:

zlib_dir:C:\dep\zlib

steps:

-uses:actions/checkout@v2

-name:Install pacman packages

run:|

-name:Make zlib

run:|

-name:Get Postgres sources

run:git clone -b REL_14_STABLE https://github.com/postgres/postgres.git

-name:Get Ptrack sources

run:|

-name:Build Postgres

run:|

-name:Build Probackup

run:cmd.exe /s /c "`"C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Auxiliary\Build\vcvarsall.bat`" amd64 && perl .\gen_probackup_project.pl `"${{ github.workspace }}`"\postgres"

-name:Install Postgres

run:|

-name:Install Testgres

run:|

-name:Test Probackup

run:|

-PG_VERSION=10 PG_BRANCH=REL_10_STABLE

-PG_VERSION=9.6 PG_BRANCH=REL9_6_STABLE

-PG_VERSION=9.5 PG_BRANCH=REL9_5_STABLE

jobs:

allow_failures:

`pg_probackup` utility is based on`pg_arman`, that was originally written by NTT and then developed and maintained by Michael Paquier.

Description of how to add new translation languages.

1. Add a flag --enable-nls in configure.

2. Build postgres.

3. Adding to nls.mk in folder pg_probackup required files in GETTEXT_FILES.

4. In folder pg_probackup do 'make update-po'.

5. As a result, the progname.pot file will be created. Copy the content and add it to the file with the desired language.

6. Adding to nls.mk in folder pg_probackup required language in AVAIL_LANGUAGES.

For more information, follow the link below:

GRANT SELECT ON TABLE pg_catalog.pg_extension TO backup;

GRANT EXECUTE ON FUNCTION bt_index_check(regclass) TO backup;

GRANT EXECUTE ON FUNCTION bt_index_check(regclass, bool) TO backup;

GRANT EXECUTE ON FUNCTION bt_index_check(regclass, bool, bool) TO backup;

</programlisting>

</refsect2>

<refsect2id="pbk-setting-up-partial-restore">

of threads with the <option>--threads</option> option:

<programlisting>

pg_probackup catchup -b <replaceable>catchup_mode</replaceable> --source-pgdata=<replaceable>path_to_pgdata_on_remote_server</replaceable> --destination-pgdata=<replaceable>path_to_local_dir</replaceable> --stream --threads=<replaceable>num_threads</replaceable>

</programlisting>

</para>

<para>

Before cloning/synchronising a <productname>PostgreSQL</productname> instance, you can run the

<command>catchup</command> command with the <option>--dry-run</option> flag

to estimate the size of data files to be transferred, but make no changes on disk:

<programlisting>

pg_probackup catchup -b <replaceable>catchup_mode</replaceable> --source-pgdata=<replaceable>path_to_pgdata_on_remote_server</replaceable> --destination-pgdata=<replaceable>path_to_local_dir</replaceable> --stream --dry-run

</programlisting>

</para>

<para>

<para>

Another example shows how you can add a new remote standby server with the <productname>PostgreSQL</productname> data directory <filename>/replica-pgdata</filename> by running the <command>catchup</command> command in the <literal>FULL</literal> mode

on four parallel threads:

<programlisting>

<programlisting>

pg_probackup catchup --source-pgdata=/master-pgdata --destination-pgdata=/replica-pgdata -p 5432 -d postgres -U remote-postgres-user --stream --backup-mode=FULL --remote-host=remote-hostname --remote-user=remote-unix-username -j 4

</programlisting>

</para>

pg_probackup checkdb

[-B <replaceable>backup_dir</replaceable>] [--instance <replaceable>instance_name</replaceable>] [-D <replaceable>data_dir</replaceable>]

[--help] [-j <replaceable>num_threads</replaceable>] [--progress]

[--skip-block-validation] [--amcheck] [--heapallindexed]

[--amcheck [--skip-block-validation] [--checkunique] [--heapallindexed]]

[<replaceable>connection_options</replaceable>] [<replaceable>logging_options</replaceable>]

</programlisting>

<para>

<para>

Performs logical verification of indexes for the specified

<productname>PostgreSQL</productname> instance if no corruption was found while checking

data files. You must have the <application>amcheck</application>

data files. You must have the <ulinkurl="https://postgrespro.com/docs/enterprise/current/amcheck.html"><application>amcheck</application></ulink>

extension or the <application>amcheck_next</application> extension

installed in the database to check its indexes. For databases

without <application>amcheck</application>, index verification will be skipped.

Additional options <option>--checkunique</option> and <option>--heapallindexed</option>

are effective depending on the version of <application>amcheck</application> installed.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term><option>--skip-block-validation</option></term>

<term><option>--checkunique</option></term>

<listitem>

<para>

Skip validation of data files. You can use this flag only

together with the <option>--amcheck</option> flag, so that only logical

verification of indexes is performed.

Verifies unique constraints during logical verification of indexes.

You can use this flag only together with the <option>--amcheck</option> flag when

the <application>amcheck</application> extension is

installed in the database.

</para>

<para>

The verification of unique constraints is only possible if in the version of the

<application>amcheck</application> extension you are using, the

<function>bt_index_check</function> function takes the

<parameter>checkunique</parameter> parameter.

</para>

</listitem>

</varlistentry>

<option>--amcheck</option> flag.

</para>

<para>

This check is only possible if you are using the

<application>amcheck</application> extension of version 2.0 or higher, or

the <application>amcheck_next</application> extension of any version.

This check is only possible if in the version of the

<application>amcheck</application>/<application>amcheck_next</application> extension

you are using, the <function>bt_index_check</function>

function takes the <parameter>heapallindexed</parameter> parameter.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term><option>--skip-block-validation</option></term>

<listitem>

<para>

Skip validation of data files. You can use this flag only

together with the <option>--amcheck</option> flag, so that only logical

verification of indexes is performed.

</para>

</listitem>

</varlistentry>

</variablelist>

</para>

<para>

pg_probackup catchup -b <replaceable>catchup_mode</replaceable>

--source-pgdata=<replaceable>path_to_pgdata_on_remote_server</replaceable>

--destination-pgdata=<replaceable>path_to_local_dir</replaceable>

[--help] [-j | --threads=<replaceable>num_threads</replaceable>] [--stream]

[--help] [-j | --threads=<replaceable>num_threads</replaceable>] [--stream] [--dry-run]

[--temp-slot] [-P | --perm-slot] [-S | --slot=<replaceable>slot_name</replaceable>]

[--exclude-path=<replaceable>PATHNAME</replaceable>]

[-T <replaceable>OLDDIR</replaceable>=<replaceable>NEWDIR</replaceable>]

</listitem>

</varlistentry>

<varlistentry>

<term><option>--dry-run</option></term>

<listitem>

<para>

Displays the total size of the files to be transferred by <command>catchup</command>.

This flag initiates a trial run of <command>catchup</command>, which does

not actually create, delete or move files on disk. WAL streaming is skipped with <option>--dry-run</option>.

This flag also allows you to check that

all the options are correct and cloning/synchronising is ready to run.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term><option>-x</option>=<replaceable>path_prefix</replaceable></term>

<term><option>--exclude-path</option>=<replaceable>path_prefix</replaceable></term>

</listitem>

</varlistentry>

<varlistentry>

<term><option>--stream</option></term>

<listitem>

<para>

Copies the instance in <linklinkend="pbk-stream-mode">STREAM</link> WAL delivery mode,

including all the necessary WAL files by streaming them from

the instance server via replication protocol.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term><option>--temp-slot</option></term>

<listitem>

{

$pgsrc =shift@ARGV;

if($pgsrceq"--help"){

printSTDERR"Usage$0 pg-source-dir\n";

printSTDERR"Like this:\n";

printSTDERR"$0 C:/PgProject/postgresql.10dev/postgrespro\n";

printSTDERR"Maybeneedinputthisbefore:\n";

printSTDERR"CALL\"C:\\Program Files (x86)\\Microsoft Visual Studio 12.0\\VC\\vcvarsall\" amd64\n";

printSTDERR"Usage$0 pg-source-dir\n";

printSTDERR"Like this:\n";

printSTDERR"$0 C:/PgProject/postgresql.10dev/postgrespro\n";

printSTDERR"May needto runthisfirst:\n";

printSTDERR"CALL\"C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Community\\VC\\Auxiliary\\Build\\vcvarsall.bat\" amd64\n";

exit 1;

}

}

unless (-d'src/tools/msvc' &&-d'src');

my$vsVersion ='12.00';

my$vsVersion ='16.00';

$solution = CreateSolution($vsVersion,$config);

'archive.c',

'backup.c',

'catalog.c',

'catchup.c',

'configure.c',

'data.c',

'delete.c',

CATALOG_NAME = pg_probackup

AVAIL_LANGUAGES = ru

GETTEXT_FILES = src/help.c

GETTEXT_TRIGGERS =$(FRONTEND_COMMON_GETTEXT_TRIGGERS)

GETTEXT_FLAGS =$(FRONTEND_COMMON_GETTEXT_FLAGS)

if [${DISTRIB}='centos' ];then

sed -i's|^baseurl=http://|baseurl=https://|g' /etc/yum.repos.d/*.repo

if [${DISTRIB_VERSION}='8' ];then

sed -i's|mirrorlist|#mirrorlist|g' /etc/yum.repos.d/CentOS-*.repo

sed -i's|#baseurl=http://mirror.centos.org|baseurl=http://vault.centos.org|g' /etc/yum.repos.d/CentOS-*.repo

yum update -y

if [${DISTRIB_VERSION}='8' ];then

sed -i's|mirrorlist|#mirrorlist|g' /etc/yum.repos.d/CentOS-*.repo

sed -i's|#baseurl=http://mirror.centos.org|baseurl=http://vault.centos.org|g' /etc/yum.repos.d/CentOS-*.repo

if [${DISTRIB}!='rhel'-o${DISTRIB_VERSION}!='7' ];then

yum update -y

if [${DISTRIB}='centos'-a${DISTRIB_VERSION}='8' ];then

sed -i's|mirrorlist|#mirrorlist|g' /etc/yum.repos.d/CentOS-*.repo

sed -i's|#baseurl=http://mirror.centos.org|baseurl=http://vault.centos.org|g' /etc/yum.repos.d/CentOS-*.repo

yum update -y

if [${DISTRIB}='centos'-a${DISTRIB_VERSION}='8' ];then

sed -i's|mirrorlist|#mirrorlist|g' /etc/yum.repos.d/CentOS-*.repo

sed -i's|#baseurl=http://mirror.centos.org|baseurl=http://vault.centos.org|g' /etc/yum.repos.d/CentOS-*.repo