Skip to main content

Posts

Featured

log_client_messages in Pgpool-II 4.0

Pgpool-II 4.0 adds new logging feature called "log_client_messages". This allows to log messages coming from frontend. Up to 3.7 the only way to log frontend messages was enable debugging log, which produced tremendous amount of logs.

For example, with log_client_messages enabled, "pgbench -S -M parepared -t 2" produces frontend logs below:

2018-12-04 16:43:45: pid 6522: LOG:  Parse message from frontend.
2018-12-04 16:43:45: pid 6522: DETAIL:  statement: "P0_1", query: "SELECT abalance FROM pgbench_accounts WHERE aid = $1;"
2018-12-04 16:43:45: pid 6522: LOG:  Sync message from frontend.
2018-12-04 16:43:45: pid 6522: LOG:  Bind message from frontend.
2018-12-04 16:43:45: pid 6522: DETAIL:  portal: "", statement: "P0_1"
2018-12-04 16:43:45: pid 6522: LOG:  Describe message from frontend.
2018-12-04 16:43:45: pid 6522: DETAIL:  portal: ""
2018-12-04 16:43:45: pid 6522: LOG:  Execute message from frontend.
2018-12-04 16:43:45:…

Latest Posts

Pgpool-II 4.0 released! (SCRAM authentication)

Even more fine load balancing control with Pgpool-II 4.0

statement_timeout changed in PostgreSQL 11

More load balancing fine control

Detecting "false" primary server of PostgreSQL

Celebrating 15th anniversary of Pgpool and next version number

Let's start Pgpool-II 3.8 development!

Importing PostgreSQL 9.6's SQL parser

New Pgpool-II mascot logo!

Avoiding session disconnection while fail over