Troubleshooting

This section contains some ideas for troubleshooting common problems experienced with Managed Service for TimescaleDB.

Permission denied when changing ownership of tables and hypertables

`

  1. ERROR: permission denied for schema _timescaledb_internal

`

You might see this error when using the ALTER TABLE command to change the ownership of tables or hypertables.

This use of ALTER TABLE is blocked because the tsdbadmin user is not a superuser.

To change table ownership, use the REASSIGN command instead:

  2. REASSIGN OWNED BY <current_role> TO <desired_role>

Service is running low on disk, memory, or CPU

`

  1. Your Managed Service for TimescaleDB service, in project "ExampleAccount", is running low on

`

`

  1. CPU. Running low on CPU affects performance and could affect service

`

`

  1. availability. Please either optimize your usage pattern or reduce the workload,

`

`

  1. and consider upgrading to a larger plan to avoid service outage.

`

When your database reaches 90% of your allocated disk, memory, or CPU resources, an automated message with the text above is sent to your email address.

You can resolve this by logging in to your Managed Service for TimescaleDB account and increasing your available resources. From the Managed Service for TimescaleDB Dashboard, select the service that you want to increase resources for. In the Overview tab, locate the Service Plan section, and click Upgrade Plan. Select the plan that suits your requirements, and click Upgrade to enable the additional resources.

If you run out of resources regularly, you might need to consider using your resources more efficiently. Consider enabling compression, using continuous aggregates, or configuring data retention to reduce the amount of resources your database uses. If you still need help, reach out to our support team to have a conversation.

Problem resolving DNS

Managed Service for TimescaleDB services require a DNS record. When you launch a new service the DNS record is created, and it can take some time for the new name to propagate to DNS servers around the world.

If you move an existing service to a new Cloud provider or region, the service is rebuilt in the new region in the background. When the service has been rebuilt in the new region, the DNS records are updated. This could cause a short interruption to your service while the DNS changes are propagated.

If you are unable to resolve DNS, wait a few minutes and try again.