A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/orgrim/pg_back/commit/47e981208ffebc61860cba68a5af690872d1c145 below:

Update docs changelog and contributors · orgrim/pg_back@47e9812 · GitHub

File tree Expand file treeCollapse file tree 3 files changed

+24

-6

lines changed

Filter options

Expand file treeCollapse file tree 3 files changed

+24

-6

lines changed Original file line number Diff line number Diff line change

@@ -3,6 +3,10 @@

3 3

## pg_back 2.6.0

4 4 5 5

* Allow to override the connection user per database

6 +

* Add the --delete-uploaded to delete local file after upload

7 +

* Add the --backup-file-mode option to configure the permissions on dumps

8 +

* Add the --uniform-timestamp option to create all files of a run with the same

9 +

time in the filenames

6 10 7 11

## pg_back 2.5.0

8 12 Original file line number Diff line number Diff line change

@@ -16,3 +16,5 @@ Massimo Lusetti

16 16

Kenny Root

17 17

Pierrick Chovelon

18 18

Dennis Urban

19 +

Julian Vanden Broeck

20 +

Stéphane Klein

Original file line number Diff line number Diff line change

@@ -66,12 +66,6 @@ If default and command line options are not enough, a configuration file

66 66

may be provided with `-c <configfilename>` (see [pg_back.conf](pg_back.conf)).

67 67

(Note: see below to convert configuration files from version 1.)

68 68 69 -

If the default output directory `/var/backups/postgresql` does not exist or has

70 -

improper ownership for your user, use `-b` to give the path where to store the

71 -

files. The path may contain the `{dbname}` keyword, that would be replaced by

72 -

the name of the database being dumped, this permits to dump each database in

73 -

its own directory.

74 - 75 69

To connect to PostgreSQL, use the `-h`, `-p`, `-U` and `-d` options. If you

76 70

need less known connection options such as `sslcert` and `sslkey`, you can give

77 71

a `keyword=value` libpq connection string like `pg_dump` and `pg_dumpall`

@@ -83,6 +77,24 @@ The other command line options let you tweak what is dumped, purged, and how

83 77

it is done. These options can be put in a configuration file. The command line

84 78

options override configuration options.

85 79 80 +

### Output

81 + 82 +

If the default output directory `/var/backups/postgresql` does not exist or has

83 +

improper ownership for your user, use `-b` to give the path where to store the

84 +

files. The path may contain the `{dbname}` keyword, that would be replaced by

85 +

the name of the database being dumped, this permits to dump each database in

86 +

its own directory.

87 + 88 +

By default the files are created with script file permissions, 0600, it can be

89 +

changed with the `--backup-file-mode` option. Permissions on directories are

90 +

deduced from the file mode to add the `x` bit if necessary.

91 + 92 +

A run of pg_back creates multiple files, with the date and time of their

93 +

creation in their filename. While this help finding at what time the data would

94 +

be restored, all timestamps in filename are potentially different. The

95 +

`--uniform-timestamp` changes this behavious to use the same date and time for

96 +

all files output by a run, it is the time of the first dump of the run.

97 + 86 98

### Per-database configuration

87 99 88 100

Per-database configuration can only be done with a configuration file. The

You can’t perform that action at this time.


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4