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: articles/postgresql/concepts-extensions.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -273,7 +273,7 @@ Now you can run pg_dump on the original database and then do pg_restore. After t
273
273
```SQL
274
274
SELECT timescaledb_post_restore();
275
275
```
276
-
For more details on restore method wiith Timescae enabled database see [Timescale documentation](https://docs.timescale.com/timescaledb/latest/how-to-guides/backup-and-restore/pg-dump-and-restore/#restore-your-entire-database-from-backup)
276
+
For more details on restore method wiith Timescale enabled database see [Timescale documentation](https://docs.timescale.com/timescaledb/latest/how-to-guides/backup-and-restore/pg-dump-and-restore/#restore-your-entire-database-from-backup)
277
277
278
278
279
279
### Restoring a Timescale database using timescaledb-backup
@@ -286,7 +286,7 @@ For more details on restore method wiith Timescae enabled database see [Timescal
286
286
4. Grant azure_pg_admin [role](https://www.postgresql.org/docs/11/database-roles.html) to user that will be used by [ts-restore](https://github.com/timescale/timescaledb-backup#using-ts-restore)
287
287
5. Run [ts-restore](https://github.com/timescale/timescaledb-backup#using-ts-restore) to restore database
288
288
289
-
More details on hese utilities can be found [here](https://github.com/timescale/timescaledb-backup).
289
+
More details on these utilities can be found [here](https://github.com/timescale/timescaledb-backup).
290
290
> [!NOTE]
291
291
> When using `timescale-backup` utilities to restore to Azure is that since database user names for non-flexible Azure Database for PostgresQL must use the `<user@db-name>` format, you need to replace `@` with `%40` character encoding.
0 commit comments