You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Documentation.md
+5-3Lines changed: 5 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -740,6 +740,8 @@ Maximum lifetime of an individual log file. If this value is reached, the log fi
740
740
####Connection Options
741
741
You can use these options together with[backup](#backup) and[checkdb](#checkdb) commands.
742
742
743
+
All libpq environment variables are fully[supported](https://www.postgresql.org/docs/current/libpq-envars.html).
744
+
743
745
-d dbname
744
746
--dbname=dbname
745
747
PGDATABASE
@@ -764,7 +766,7 @@ User name to connect as.
764
766
765
767
-w
766
768
--no-password
767
-
Disables a password prompt. If the server requires password authentication and a password is not available by other means such as a[.pgpass](https://www.postgresql.org/docs/current/libpq-pgpass.html) file, the connection attempt will fail. This option can be useful in batch jobs and scripts where no user is present to enter a password.
769
+
Disables a password prompt. If the server requires password authentication and a password is not available by other means such as a[.pgpass](https://www.postgresql.org/docs/current/libpq-pgpass.html) file or PGPASSWORD environment variable, the connection attempt will fail. This option can be useful in batch jobs and scripts where no user is present to enter a password.
768
770
769
771
-W
770
772
--password
@@ -895,7 +897,7 @@ For example, to make a FULL backup in ARCHIVE mode, run:
895
897
896
898
ARCHIVE backup rely on[continuous archiving](#setting-up-continuous-wal-archiving) to provide WAL segments required to restore the cluster to a consistent state at the time the backup was taken.
897
899
898
-
During[backup](#backup) pg_probackup ensures that WAL files containing WAL records between START LSN and STOP LSN are actually exists in '*backup_dir*/wal/*instance_name*' directory. Also pg_probackup ensures that WAL records between START LSN and STOP LSN can be parsed. Thiscostlyprecations eliminates the risk of silent WAL corruption.
900
+
During[backup](#backup) pg_probackup ensures that WAL files containing WAL records between START LSN and STOP LSN are actually exists in '*backup_dir*/wal/*instance_name*' directory. Also pg_probackup ensures that WAL records between START LSN and STOP LSN can be parsed. This precations eliminates the risk of silent WAL corruption.
899
901
900
902
####STREAM mode
901
903
@@ -909,7 +911,7 @@ The optional `--temp-slot` flag ensures that the required segments remain availa
909
911
910
912
STREAM backups include all the WAL segments required to restore the cluster to a consistent state at the time the backup was taken.
911
913
912
-
During[backup](#backup) pg_probackup streams WAL files containing WAL records between START LSN and STOP LSN in '*backup_dir*/backups/*instance_name*/*BACKUP ID*/database/pg_wal' directory. Also pg_probackup ensures that WAL records between START LSN and STOP LSN can be parsed. Thiscostlyprecations eliminates the risk of silent WAL corruption.
914
+
During[backup](#backup) pg_probackup streams WAL files containing WAL records between START LSN and STOP LSN in '*backup_dir*/backups/*instance_name*/*BACKUP ID*/database/pg_wal' directory. Also pg_probackup ensures that WAL records between START LSN and STOP LSN can be parsed. This precations eliminates the risk of silent WAL corruption.
913
915
914
916
Even if you are using[continuous archiving](#setting-up-continuous-wal-archiving), STREAM backups can still be useful in the following cases: