* Extended logging settings

* Custom commands to simplify WAL log archiving

* External to PGDATA directories, such as directories with config files and scripts, can be included in backup

* Remote backup, restore, archive-push and archive-get operations via ssh (beta)

* Remote backup, restore,add-instance,archive-push and archive-get operations via ssh (beta)

* Checking running PostgreSQL instance for the sights of corruption in read-only mode via`checkdb` command.

To manage backup data,`pg_probackup` creates a backup catalog. This directory stores all backup files with additional meta information, as well as WAL archives required for[point-in-time recovery](https://postgrespro.com/docs/postgresql/current/continuous-archiving.html). You can store backups for different instances in separate subdirectories of a single backup catalog.

deftruncate_every_file_in_dir(self,path):

forfileinos.listdir(path):

print(file)

withopen(os.path.join(path,file),"w")asf:

f.close()

defbackup_node(

self,backup_dir,instance,node,data_dir=False,

backup_type='full',options=[],asynchronous=False,gdb=False,

backup_type='full',datname=False,options=[],

asynchronous=False,gdb=False,

old_binary=False,return_id=True

):

ifnotnodeandnotdata_dir:

print('You must provide ether node or data_dir for backup')

exit(1)

ifnotdatname:

cmd_list= [

'backup',

'-B',backup_dir,

'--instance={0}'.format(instance),

'-p','%i'%node.port,

'-d','postgres'

'-d',datname

]

ifdata_dir: