From 6f948cb2f00bfa6d7102953ecbd2cc38a2812d6c Mon Sep 17 00:00:00 2001
From: Rajakavitha1 <krajakavitha@gmail.com>
Date: Wed, 15 Feb 2023 14:22:50 +0530
Subject: [PATCH 1/2] added ts and a note for pg_dumpall

---
 .../timescaledb/pg_restore-errors.md          | 22 +++++++++++++++++++
 .../backup-and-restore/pg-dump-and-restore.md |  8 +++++++
 2 files changed, 30 insertions(+)
 create mode 100644 _troubleshooting/timescaledb/pg_restore-errors.md

diff --git a/_troubleshooting/timescaledb/pg_restore-errors.md b/_troubleshooting/timescaledb/pg_restore-errors.md
new file mode 100644
index 0000000000..69ad314d88
--- /dev/null
+++ b/_troubleshooting/timescaledb/pg_restore-errors.md
@@ -0,0 +1,22 @@
+---
+title: Errors occur after restoring from file dump 
+section: troubleshooting
+topics: [backups]
+errors:
+  - language: bash
+    message: |-
+      org.postgresql.util.PSQLException: ERROR: invalid INSERT on the root table of hypertable "_hyper_1_10_chunk.
+keywords: [backups, restore]
+---
+
+<!---
+* Use this format for writing troubleshooting sections:
+ - Cause: What causes the problem?
+ - Consequence: What does the user see when they hit this problem?
+ - Fix/Workaround: What can the user do to fix or work around the problem? Provide a "Resolving" Procedure if required.
+ - Result: When the user applies the fix, what is the result when the same action is applied?
+* Copy this comment at the top of every troubleshooting page
+-->
+ You might see the errors above when running `pg_restore`. When loading from a
+ logical dump make sure you set `timescaledb.restoring` to true before loading
+ the dump.
diff --git a/timescaledb/how-to-guides/backup-and-restore/pg-dump-and-restore.md b/timescaledb/how-to-guides/backup-and-restore/pg-dump-and-restore.md
index afb03181b2..94acade331 100644
--- a/timescaledb/how-to-guides/backup-and-restore/pg-dump-and-restore.md
+++ b/timescaledb/how-to-guides/backup-and-restore/pg-dump-and-restore.md
@@ -168,6 +168,13 @@ partitions, or the chunk interval sizes.
 
 </procedure>
 
+On a self hosted TimescaleDb instance with `postgres` superuser access you can
+take a complete dump of all PostgreSQL databases in a cluster including global
+objects that are common to all databases, namely database roles, tablespaces,
+and privilege grants for configuration parameters using `pg_dumpall`. For more
+information about how to use the `pg_dumpall` utility, see
+[PostgreSQL documentation][postgres-docs].  
+
 [parallel importer]: https://github.com/timescale/timescaledb-parallel-copy
 [pg_dump]: https://www.postgresql.org/docs/current/static/app-pgdump.html
 [pg_restore]: https://www.postgresql.org/docs/current/static/app-pgrestore.html
@@ -175,3 +182,4 @@ partitions, or the chunk interval sizes.
 [timescaledb_post_restore]: /api/:currentVersion:/administration/timescaledb_post_restore/
 [timescaledb-upgrade]: /timescaledb/:currentVersion:/how-to-guides/upgrades/
 [troubleshooting]: /timescaledb/:currentVersion:/how-to-guides/backup-and-restore/troubleshooting/
+[postgres-docs]: https://www.postgresql.org/docs/current/app-pg-dumpall.html

From 9b541e07a00f597f2e3c7d2792d373e48e463f40 Mon Sep 17 00:00:00 2001
From: Rajakavitha1 <krajakavitha@gmail.com>
Date: Wed, 15 Feb 2023 14:42:50 +0530
Subject: [PATCH 2/2] minor edits

---
 _troubleshooting/timescaledb/pg_restore-errors.md             | 2 +-
 .../how-to-guides/backup-and-restore/pg-dump-and-restore.md   | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/_troubleshooting/timescaledb/pg_restore-errors.md b/_troubleshooting/timescaledb/pg_restore-errors.md
index 69ad314d88..a657a4567c 100644
--- a/_troubleshooting/timescaledb/pg_restore-errors.md
+++ b/_troubleshooting/timescaledb/pg_restore-errors.md
@@ -18,5 +18,5 @@ keywords: [backups, restore]
 * Copy this comment at the top of every troubleshooting page
 -->
  You might see the errors above when running `pg_restore`. When loading from a
- logical dump make sure you set `timescaledb.restoring` to true before loading
+ logical dump make sure that you set `timescaledb.restoring` to true before loading
  the dump.
diff --git a/timescaledb/how-to-guides/backup-and-restore/pg-dump-and-restore.md b/timescaledb/how-to-guides/backup-and-restore/pg-dump-and-restore.md
index 94acade331..9a43c077c7 100644
--- a/timescaledb/how-to-guides/backup-and-restore/pg-dump-and-restore.md
+++ b/timescaledb/how-to-guides/backup-and-restore/pg-dump-and-restore.md
@@ -168,10 +168,10 @@ partitions, or the chunk interval sizes.
 
 </procedure>
 
-On a self hosted TimescaleDb instance with `postgres` superuser access you can
+On a self hosted TimescaleDB instance with `postgres` superuser access you can
 take a complete dump of all PostgreSQL databases in a cluster including global
 objects that are common to all databases, namely database roles, tablespaces,
-and privilege grants for configuration parameters using `pg_dumpall`. For more
+and privilege grants using `pg_dumpall`. For more
 information about how to use the `pg_dumpall` utility, see
 [PostgreSQL documentation][postgres-docs].