[pgpool-general: 9313] Re: pgpool Connection issue: ERROR: unable to read message kind

Tatsuo Ishii ishii at postgresql.org
Thu Jan 2 19:29:39 JST 2025


> Hello Tatsuo,
> 
> *Have you set synchronous_standby_names parameter in postgresql.conf?*
> YES. we set it. Please see below:
> 
> [pgbigboss at azlpgN1hS-0 ~]$ cat /u01/app/admin/Data/PG_DATA/postgresql.conf
> | grep -v '^#' |egrep '^[^[:space:]]' | grep sync
> synchronous_commit = remote_apply
> synchronous_standby_names = 'ANY 1 (azlpgNPBC2, azlpgN1hS0, azlpgN6Xm1)'

I think the synchronous_standby_names setting is not appropreate here.
With this setting PostgreSQL will respond as soon as *one* of standby
servers replies back that replication is done. This means other two
servers do not yet replicate the data. As a result pgpool could
connect to one of the yet-replicated standby servers, that do not have
the newly created database yet, and pgpool reports it as an "kind
mismatch error". Probably you should set:

synchronous_standby_names = 'ANY 3 (azlpgNPBC2, azlpgN1hS0, azlpgN6Xm1)'

BTW, previously you said you only have 1 standby server. But it seems
actually you have 3 standby servers?

> backend_hostname0 = '10.35.8.30'
> backend_port0 = 5432
> backend_weight0 = 1
> backend_hostname1 = '10.35.8.31'
> backend_port1 = 5432
> backend_weight1 = 1

Best reagards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp


More information about the pgpool-general mailing list