pg_timetable running against read-only replica

[pashagolub]

Discussed in #563

^{Originally posted by seanzechman May 16, 2023}
We have pg_timetable daemon running locally on all of our postgres servers. We are testing a POC and noticed that on read-only replicas pg_timetable takes all of available connections. Is this by design and is there a way to stop the build up of sessions? We would like pg_timetable to work after a failover to a standby node but right now our standby node has issues because max_connections is reached due to this problem

[notice:Cannot obtain lock on a replica. Please, use the primary node] [severity:NOTICE] #33[0mNotice received

pg_timetable:
Version: 5.3.0
DB Schema: 00534
Git Commit: e6a13ee
Built: 2023-03-13T11:38:30Z