Help Center > > FAQs> Database Parameter Modification> What Inappropriate Parameter Settings Cause Unavailability of the PostgreSQL Database?

What Inappropriate Parameter Settings Cause Unavailability of the PostgreSQL Database?

Updated at: Apr 20, 2020 GMT+08:00

In the following cases, inappropriate parameter settings cause unavailability of the database:

  • Parameter value ranges are related to DB instance specifications.

    The maximum values of shared_buffers and max_connections are related to the DB instance physical memory. If you set the parameters inappropriately, the database is unavailable.

  • Parameter association is incorrect.
    • If log_parser_stats, log_planner_stats, or log_executor_stats is enabled, you must disable log_statement_stats. Otherwise, the database is unavailable.
    • max_connections, autovacuum_max_workers, and max_worker_processes must meet the following requirements. Otherwise, the database is unavailable.

      max_connections value + autovacuum_max_workers value + max_worker_processes value + 1 < 8388607

For details on parameter descriptions, visit the PostgreSQL official website.

Solution:

  1. Log in to the RDS console and query the logs to locate the incorrectly configured parameter.
  2. On the Configuration page, change parameters to default values and reboot the database.
  3. Set the incorrectly configured parameter to a correct value and other parameters to the original values.

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel