本篇内容主要讲解“PostgreSQL 12在日志记录上的改进是什么”，感兴趣的朋友不妨来看看。本文介绍的方法操作简单快捷，实用性强。下面就让小编来带大家学习“PostgreSQL 12在日志记录上的改进是什么”吧!

对于每一个客户端连接，PG都会请求Postmaster，然后fork一个后台进程来处理请求，Postmaster期望每一个客户端请求发送startup message给PG Server，startup packet中的信息用于配置fork的后台进程。对于端口扫描、HA解决方案中的心跳检测等等都会发请求给PG Server port，PG会启动进程来处理这些连接，但安全检测、HA脚本等不同于常规的客户端，对于这些请求，PG会产生一条日志条目，因此会造成日志文件的膨胀而导致不必要的IO开销。

PG 11
使用工具nc来访问数据库端口，日志中会产生无用的日志条目。

[xdb@localhost~]$psql-c'selectversion();'Timingison.Expandeddisplayisusedautomatically.version---------------------------------------------------------------------------------------------------------PostgreSQL11.2onx86_64-pc-linux-gnu,compiledbygcc(GCC)4.8.520150623(RedHat4.8.5-16),64-bit(1row)Time:56.253ms[xdb@localhost~]$[xdb@localhost~]$foriin{1..100};donc-zvlocalhost5110;doneNcat:0bytessent,0bytesreceivedin0.01seconds.Ncat:Version7.50(https://nmap.org/ncat)Ncat:Connectedto::1:5110.Ncat:0bytessent,0bytesreceivedin0.01seconds.Ncat:Version7.50(https://nmap.org/ncat)Ncat:Connectedto::1:5110.Ncat:0bytessent,0bytesreceivedin0.01seconds.Ncat:Version7.50(https://nmap.org/ncat)Ncat:Connectedto::1:5110.Ncat:0bytessent,0bytesreceivedin0.01seconds.Ncat:Version7.50(https://nmap.org/ncat)Ncat:Connectedto::1:5110.Ncat:0bytessent,0bytesreceivedin0.01seconds....

数据库日志输出

2019-12-0914:35:55.468CST,,,16065,"::1:57554",5dedeb4b.3ec1,1,"",2019-12-0914:35:55CST,,0,LOG,08P01,"incompletestartuppacket",,,,,,,,,""2019-12-0914:35:55.479CST,,,16067,"::1:57556",5dedeb4b.3ec3,1,"",2019-12-0914:35:55CST,,0,LOG,08P01,"incompletestartuppacket",,,,,,,,,""2019-12-0914:35:55.490CST,,,16069,"::1:57558",5dedeb4b.3ec5,1,"",2019-12-0914:35:55CST,,0,LOG,08P01,"incompletestartuppacket",,,,,,,,,""2019-12-0914:35:55.503CST,,,16071,"::1:57560",5dedeb4b.3ec7,1,"",2019-12-0914:35:55CST,,0,LOG,08P01,"incompletestartuppacket",,,,,,,,,""2019-12-0914:35:55.513CST,,,16073,"::1:57562",5dedeb4b.3ec9,1,"",2019-12-0914:35:55CST,,0,LOG,08P01,"incompletestartuppacket",,,,,,,,,""...

这些日志其实是无用的日志信息，可以不作记录。

PG 12

[xdb@localhost~]$psql-hlocalhost-p5120-Upg12-c'selectversion();'Timingison.Expandeddisplayisusedautomatically.version---------------------------------------------------------------------------------------------------------PostgreSQL12.1onx86_64-pc-linux-gnu,compiledbygcc(GCC)4.8.520150623(RedHat4.8.5-16),64-bit(1row)Time:60.207ms[xdb@localhost~]$[xdb@localhost~]$foriin{1..100};donc-zvlocalhost5120;doneNcat:0bytessent,0bytesreceivedin0.01seconds.Ncat:Version7.50(https://nmap.org/ncat)Ncat:Connectedto::1:5120.Ncat:0bytessent,0bytesreceivedin0.01seconds.Ncat:Version7.50(https://nmap.org/ncat)Ncat:Connectedto::1:5120.Ncat:0bytessent,0bytesreceivedin0.01seconds.Ncat:Version7.50(https://nmap.org/ncat)Ncat:Connectedto::1:5120.Ncat:0bytessent,0bytesreceivedin0.01seconds.Ncat:Version7.50(https://nmap.org/ncat)Ncat:Connectedto::1:5120.Ncat:0bytessent,0bytesreceivedin0.01seconds.Ncat:Version7.50(https://nmap.org/ncat)Ncat:Connectedto::1:5120.Ncat:0bytessent,0bytesreceivedin0.01seconds.[xdb@localhost~]$...

数据库日志信息，相对于PG 11，没有出现无用的日志信息

[pg12@localhost~]$tail-f$PGDATA/pg_log/postgresql-2019-12-09.log2019-12-0914:18:59.317CST[1813]LOG:endinglogoutputtostderr2019-12-0914:18:59.317CST[1813]HINT:Futurelogoutputwillgotologdestination"csvlog".

到此，相信大家对“PostgreSQL 12在日志记录上的改进是什么”有了更深的了解，不妨来实际操作一番吧！这里是亿速云网站，更多相关内容可以进入相关频道进行查询，关注我们，继续学习！