[pgpool-general: 8529] Re: "delay_threshold_by_time" not detecting replication lag

[Tatsuo Ishii]

> OK, This seems to be working now.

Good.

> I made changes to pgpool.conf
>   backend_application_name0 = 'primary'
>   backend_application_name1 = 'replica_1'
> Then, on standby/replica server #1, in the PostgreSQL config, setting
> for "primary_conninfo", I added "application_name=replica_1"
> After that, I repeated my test as previously and I could see log entries.
> 
> I guess I missed this because the previous setting I used
> (delay_threshold) did not seem to depend on application_name in
> replicas' primary_conninfo parameter...
> May I suggest adding some clarification in docs for
> "delay_threshold_by_time" - something like:
> "delay_threshold_by_time relies on backend_application_name  being
> correctly set and matching application_name in your
> PostgreSQLreplica's primary_conninfo"

Sounds like a nice idea. Thanks for the suggestion. Doc patch
attached.

> Also, since "pimary_conninfo" is only relevant to PostgreSQL replicas
> (setting has no effect if the server is not in standby mode),
> is it safe to say that "backend_application_name0" does not matter in
> the config?

I don't think so because Pgpool-II backend0 is not necessarily a
primary node unless ALWAYS_PRIMARY flag is set to the node.

> 
> Once again thanks for the help!
> Z..

You are welcome!

Best reagards,
--
Tatsuo Ishii
SRA OSS LLC
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: delay_threshold_by_time.patch
Type: text/x-patch
Size: 1329 bytes
Desc: not available
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20221229/551bbbdd/attachment.bin>