This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Choose the best response for each of the questions below.
You've recently taken over support for an Azure Database for PostgreSQL database in your company. You've noticed that the amount of storage required for the database appears to be growing at a rate greater than you would expect. What should you do to investigate?
Check the server parameters to ensure autovacuum is switched OFF.
Prevent users from adding more data to the database until the problem has been solved.
Run a SELECT query to find dead rows that are no longer needed in the database.
You've tuned the server parameters to make autovacuum more efficient. However, users are complaining of slight delays when updating the single table in your database that has most updates. What could you do to resolve the problem?
Split the table into two.
Increase the value for autovacuum_analyze_threshold.
Disable AUTOVACUUM and run VACUUM manually as required.
As part of an annual routine, a large number of records have been updated. This has been done over a holiday when your Azure Database for PostgreSQL database isn't in use. Now that the updates are complete, what should you do to ensure lost disk space is reclaimed?
Manually run VACUUM.
Increase the autovacuum_work_mem.
Disable AUTOVACUUM and manually run VACUUM.
You must answer all questions before checking your work.
Was this page helpful?
Need help with this topic?
Want to try using Ask Learn to clarify or guide you through this topic?