... | @@ -556,7 +556,7 @@ estimates_with_toast AS ( |
... | @@ -556,7 +556,7 @@ estimates_with_toast AS ( |
|
table_estimates_plus AS (
|
|
table_estimates_plus AS (
|
|
-- add some extra metadata to the table data
|
|
-- add some extra metadata to the table data
|
|
-- and calculations to be reused
|
|
-- and calculations to be reused
|
|
-- including whether we cant estimate it
|
|
-- including whether we can't estimate it
|
|
-- or whether we think it might be compressed
|
|
-- or whether we think it might be compressed
|
|
SELECT current_database() as databasename,
|
|
SELECT current_database() as databasename,
|
|
schemaname, tablename, can_estimate,
|
|
schemaname, tablename, can_estimate,
|
... | @@ -896,7 +896,7 @@ the BASE file manually on the server. |
... | @@ -896,7 +896,7 @@ the BASE file manually on the server. |
|
If you get this error in the PostgreSQL restore logs:
|
|
If you get this error in the PostgreSQL restore logs:
|
|
|
|
|
|
No directories from which read is allowed given on cmdline.
|
|
No directories from which read is allowed given on cmdline.
|
|
Unkown format in line 1 () when getting dictyotum:main.WAL.00000005.history from backup host
|
|
Unknown format in line 1 () when getting dictyotum:main.WAL.00000005.history from backup host
|
|
|
|
|
|
It's because the SSH keys deployed on the server does not have the
|
|
It's because the SSH keys deployed on the server does not have the
|
|
`--read-allowed` argument.
|
|
`--read-allowed` argument.
|
... | @@ -1384,7 +1384,7 @@ procedure because files are copied around twice: once from the backup |
... | @@ -1384,7 +1384,7 @@ procedure because files are copied around twice: once from the backup |
|
server, and again loaded in the database.
|
|
server, and again loaded in the database.
|
|
|
|
|
|
Both procedures are adaptations of the [official recovery
|
|
Both procedures are adaptations of the [official recovery
|
|
procedure](https://www.postgresql.org/docs/11/continuous-archiving.html#BACKUP-PITR-RECOVERY), which can be refered to for more information.
|
|
procedure](https://www.postgresql.org/docs/11/continuous-archiving.html#BACKUP-PITR-RECOVERY), which can be referred to for more information.
|
|
|
|
|
|
See the procedures in [direct backup recovery](#direct-backup-recovery) and [indirect backup
|
|
See the procedures in [direct backup recovery](#direct-backup-recovery) and [indirect backup
|
|
recovery](#indirect-backup-recovery), above.
|
|
recovery](#indirect-backup-recovery), above.
|
... | | ... | |