• begin; explain analyze query; rollback; • create index CONCURRENTLY idx on tbl(id); • 密码复杂度、认证方法 • 业务系统，开发测试账号，不要使用数据库超 级用户。 • 长连接relcache , syscache • 数据隔离(cluster -> database -> schema) • 主备切换(prewarm)

--unit postgresql # systemctl enable postgresql # systemctl start postgresql 如果想安装其他版本，可到官网查询安装方法 h�ps://www.postgresql.org/download/linux/redhat/ 本文档选择PG-13版本作为讲解，使用el8系列的系统，x86_64平台 # yum install

Increase checkpoint_segments .................................................................224 13.4.6. Run ANALYZE Afterwards...............................................................................225 ...................................................................................245 16. Server Run-time Environment ................................................................................. Connection Problems ...........................................................................249 16.4. Run-time Configuration................................................................................

Increase checkpoint_segments ..........................................................213 13.4.6. Run ANALYZE Afterwards........................................................................213 III Windows................................................................................232 16. Server Run-time Environment ................................................................................. Connection Problems ....................................................................236 16.4. Run-time Configuration................................................................................

Error Reporting and Logging ............................................................... 621 20.9. Run-time Statistics ............................................................................. 633 20 miss the problem. The best format for a test case for SQL-related problems is a file that can be run through the psql frontend that shows the problem. (Be sure to not have anything in your ~/.psqlrc start-up \set VERBOSITY verbose beforehand. If you are extracting the message from the server log, set the run-time parameter log_error_verbosity to verbose so that all details are logged. Note In case of fatal

Reporting and Logging ..................................................................... 653 20.9. Run-time Statistics .................................................................................. miss the problem. The best format for a test case for SQL-related problems is a file that can be run through the psql frontend that shows the problem. (Be sure to not have anything in your ~/.psqlrc start-up \set VERBOSITY verbose beforehand. If you are extracting the message from the server log, set the run-time parameter log_error_verbosity to verbose so that all details are logged. Note In case of fatal

Error Reporting and Logging ............................................................... 602 19.9. Run-time Statistics ............................................................................. 613 19 miss the problem. The best format for a test case for SQL-related problems is a file that can be run through the psql frontend that shows the problem. (Be sure to not have anything in your ~/.psqlrc start-up \set VERBOSITY verbose beforehand. If you are extracting the message from the server log, set the run-time parameter log_error_verbosity to verbose so that all details are logged. Note In case of fatal

Reporting and Logging ..................................................................... 636 19.9. Run-time Statistics .................................................................................. miss the problem. The best format for a test case for SQL-related problems is a file that can be run through the psql frontend that shows the problem. (Be sure to not have anything in your ~/.psqlrc start-up \set VERBOSITY verbose beforehand. If you are extracting the message from the server log, set the run-time parameter log_error_verbosity to verbose so that all details are logged. Note In case of fatal

Error Reporting and Logging ............................................................... 542 19.9. Run-time Statistics ............................................................................. 552 19 miss the problem. The best format for a test case for SQL-related problems is a file that can be run through the psql frontend that shows the problem. (Be sure to not have anything in your ~/.psqlrc start-up \set VERBOSITY verbose beforehand. If you are extracting the message from the server log, set the run-time parameter log_error_verbosity to verbose so that all details are logged. Note In case of fatal

Error Reporting and Logging ............................................................... 600 19.9. Run-time Statistics ............................................................................. 611 19 miss the problem. The best format for a test case for SQL-related problems is a file that can be run through the psql frontend that shows the problem. (Be sure to not have anything in your ~/.psqlrc start-up \set VERBOSITY verbose beforehand. If you are extracting the message from the server log, set the run-time parameter log_error_verbosity to verbose so that all details are logged. Note In case of fatal