{[user-guide-os]} packages for are available at apt.postgresql.org. If they are not provided for your distribution/version it is easy to download the source and install manually.
+
{[user-guide-os]} packages for are available at apt.postgresql.org. If they are not provided for your distribution/version it is easy to download the source and install manually.
-
{[user-guide-os]} packages for are available from Crunchy Data or yum.postgresql.org, but it is also easy to download the source and install manually.
+
{[user-guide-os]} packages for are available from Crunchy Data or yum.postgresql.org, but it is also easy to download the source and install manually.
By default {[user-guide-os]} includes the day of the week in the log filename. This makes automating the user guide a bit more complicated so the log_filename is set to a constant.
+
By default {[user-guide-os]} includes the day of the week in the log filename. This makes automating the user guide a bit more complicated so the log_filename is set to a constant.
-
+ Set log_filename'postgresql.log'
@@ -1015,7 +1019,7 @@
Attempt to start the corrupted {[postgres-cluster-demo]} cluster
-
+ {[pg-cluster-start]}could not find the database system
@@ -1024,15 +1028,15 @@
{[pg-cluster-wait]}
-
+ rm -f {[postgres-log-pgstartup-demo]}
-
+ {[pg-cluster-start]}
-
+ cat {[postgres-log-pgstartup-demo]}errorcould not find the database system
@@ -1244,7 +1248,7 @@
-
+ Using jq
jq is a command-line utility that can easily extract data from JSON.
By default {[user-guide-os]} stores the postgresql.conf file in the data directory. That means the change made to postgresql.conf was overwritten by the last restore and the hot_standby setting must be enabled again. Other solutions to this problem are to store the postgresql.conf file elsewhere or to enable the hot_standby setting on the {[host-pg1]} host where it will be ignored.
+
By default {[user-guide-os]} stores the postgresql.conf file in the data directory. That means the change made to postgresql.conf was overwritten by the last restore and the hot_standby setting must be enabled again. Other solutions to this problem are to store the postgresql.conf file elsewhere or to enable the hot_standby setting on the {[host-pg1]} host where it will be ignored.