[pgpool-general: 8541] Re: pgpool version 4.4 with postgres version 14
Tatsuo Ishii
ishii at sraoss.co.jp
Fri Jan 13 07:36:49 JST 2023
> Hello,
>
> currently we are using pgpool version 4.4 with postgres version 14 but the
> pgpool has issue in get replication status as per below error from postgres
> logs:
>
>
>
> *pgpool at postgres LOG: could not receive data from client: Connection reset
> by peer2023-01-09 11:00:16.890 EET [2206798] pgpool at postgres ERROR:
> integer out of range2023-01-09 11:00:16.890 EET [2206798] pgpool at postgres
> STATEMENT: SELECT application_name, state, sync_state,(EXTRACT(EPOCH FROM
> replay_lag)*1000000)::integer FROM pg_stat_replication*
>
> so, is there any solution or workaround for this issue?
Sounds like replay_lag was too much and the result ((EXTRACT(EPOCH
FROM replay_lag)*1000000) was too large for integer. Probably the
delay was over 36 minutes or so (36*60*1000000 = 2160000000 >
2147483647 (integer max)). I think we can fix this by using bigint or
int8 instead of integer here but it requires modification to the
source code. Unless you can build from the source code, the only
workaround is stopping using delay_threshold_by_time
(i.e. delay_threshold_by_time = 0) and using ordinal delay_threshold
which is based on bytes rather than time.
Best reagards,
--
Tatsuo Ishii
SRA OSS LLC
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
More information about the pgpool-general
mailing list