Shulou(Shulou.com)05/31 Report--

This article focuses on "analyzing the issues related to parameter setting and transactions in PostgreSQL". Interested friends may wish to have a look at it. The method introduced in this paper is simple, fast and practical. Now let the editor to take you to learn "Analysis of parameter settings and transaction-related issues in PostgreSQL"!

As shown in the following example, the transaction is started, parameters are set, modifications are written to the pg_setting, the transaction is rolled back, and the relevant configuration is rolled back.

[local:/data/run/pg12]: 5120 pg12@testdb=# begin;BEGIN [local:/data/run/pg12]: 5120 pg12@testdb=#* show enable_seqscan; enable_seqscan-on (1 row) [local:/data/run/pg12]: 5120 pg12@testdb=#* set enable_seqscan=off;SET [local:/data/run/pg12]: 5120 pg12@testdb=#* select name,setting from pg_settings where name = 'enable_seqscan' Name | setting-+-enable_seqscan | off (1 row) [local:/data/run/pg12]: 5120 pg12@testdb=#* rollback;ROLLBACK [local:/data/run/pg12]: 5120 pg12@testdb=# select name,setting from pg_settings where name = 'enable_seqscan' Name | setting-+-enable_seqscan | on (1 row) [local:/data/run/pg12]: 5120 pg12@testdb=#. I believe you have a better understanding of "analyzing parameter settings and transaction-related issues in PostgreSQL". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.