Hi, @Soham Rajeshbhai Soneji There is an issue with time-scaled extension integration with flexible servers PostgreSQL 13 related to internal role ownership. We will fix this in a later release, we do not have steps to mitigate at this time however Potential Adhoc mitigation that you can perform if you would like to, also the support team will provide you with more information.
The steps would roughly be..
- created a database as azure_pg_admin user
- enabled timescaledb as azure_pg_admin user
- created a table in the database as azure_pg_admin user
- converted the table to timescaledb hypertable as azure_pg_admin user
- executed "pg_dump -Fc -f exampledb.bak exampledb" as azure_pg_admin user to backup database
- created a new database as azure_pg_admin user
- enabled timescaledb as azure_pg_admin user
- executed "select public.timescaledb_pre_restore();" as azuresu
- executed "pg_restore -Fc -d new_exampledb exampledb.bak" as azure_pg_admin user
- executed "select public.timescaledb_post_restore();" as azuresu
while using the pg_dump and pg_restore to restore a Timescale database is a known issue, our product team is still working to fix this issue.
They have also suggested to try using the timescledb-backup option to restore the Timescale database by following the link below.
Restoring a Timescale database using timescaledb-backup
https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-extensions#restoring-a-timescale-database-using-timescaledb-backup
Please let us know if this information is helpful.
Regards
Geetha