Re: PG-15.6: timeout parameters erroring out

2025-02-10 Thread Mukesh Tanuku
Thanks for all of you for responding and clarifying things. Really appreciate it. We finally confirmed that it is a SET command issue where the AWX application is firing the query without quotes and it's a known bug from their end. Thank you once again. Regards Mukesh Tanuku On Mon, F

Re: PG-15.6: timeout parameters erroring out

2025-02-10 Thread Mukesh Tanuku
I see there is some open PR in awx-operator ( https://github.com/ansible/awx/issues/15406) which is related to this. AWX is connected to DB in my case. On Mon, Feb 10, 2025 at 7:04 PM Mukesh Tanuku wrote: > Thanks for clarifying, got it. > Is this issue specifically reported in only the

Re: PG-15.6: timeout parameters erroring out

2025-02-10 Thread Mukesh Tanuku
Thanks for clarifying, got it. Is this issue specifically reported in only the PG 15 version? more syntax sensitivity. On Mon, Feb 10, 2025 at 6:09 PM rob stone wrote: > > > On Mon, 2025-02-10 at 16:06 +0530, Mukesh Tanuku wrote: > > Thanks for your quick responses. > >

Re: PG-15.6: timeout parameters erroring out

2025-02-10 Thread Mukesh Tanuku
[2531150] ERROR: trailing junk after numeric literal at or near "80s" at character 43 2025-02-10 10:27:16.117 GMT [2531150] STATEMENT: SET idle_in_transaction_session_timeout = 80s though we are not firing any SQL statements explicitly we see this error. i guess something else is

PG-15.6: timeout parameters erroring out

2025-02-09 Thread Mukesh Tanuku
pilled up and reaching max connections. I really appreciate your help. Thank you. Regards Mukesh Tanuku

pgpool Connection issue: ERROR: unable to read message kind

2024-12-20 Thread Mukesh Tanuku
failed connection to server at "10.35.8.4", port failed: ERROR: unable to read message kind DETAIL: kind does not match between main(53) slot[1] (45) If you want to see any configuration settings that i made, i can share. Please help me in this regard. Thank you Mukesh Tanuku

repmgr 5.4.1 dependend package on RHEL9

2024-10-13 Thread Mukesh Tanuku
Hello everyone, Question: We are installing *repmgr 5.4.1* along with postgres 15.6 on RHEL 9 and facing an issue with the dependent development package json-c *-devel-0.14-11.el9.x86_64**. *This package is not available on RHEL repository so we have to enable EPEL repo (EPEL repository is a comm

Re: Replication lag in Postgres

2024-07-12 Thread Mukesh Tanuku
Thank you for the information Laurenz Albe On Fri, Jul 12, 2024 at 9:13 PM Laurenz Albe wrote: > On Fri, 2024-07-12 at 20:41 +0530, Mukesh Tanuku wrote: > > I have a question with postgres HA setup. > > We are setting up a 2 node postgres cluster with async streaming > repli

Replication lag in Postgres

2024-07-12 Thread Mukesh Tanuku
Hello everyone. Firstly thanks to the community members who are addressing all the queries that are posted. Those give us more insights about the issues/doubts in the postgres. I have a question with postgres HA setup. We are setting up a 2 node postgres cluster with async streaming replication, w

Query 2 Node HA test case result

2024-07-03 Thread Mukesh Tanuku
Hello everyone, We are doing a POC on postgres HA setup with streaming replication (async) using pgpool-II as a load balancing & connection pooling and repmgr for setting up HA & automatic failover. We are applying a test case, like isolating the VM1 node from the Network completely for more than

Pgpool delegate IP is not reachable from the remote host

2024-06-18 Thread Mukesh Tanuku
at we disabled the if_* commands in the configuration and started pgpool, but VIP is getting acquired by the leader pgpool node even the if_* commands are not used in pgpool.conf file. Can anyone explain how the VIP works in pgpool watchdog Thank you Regards Mukesh Tanuku

Re: [pgpool-general: 9106] Postgres/pgpool HA failover process

2024-05-30 Thread Mukesh Tanuku
BTW here is the network configuration we set as UTOCONNECT_PRIORITY=120 BOOTPROTO=dhcp DEVICE=eth0 DHCPV6C=yes HWADDR= IPV6INIT=yes ONBOOT=yes TYPE=Ethernet USERCTL=no Regards Mukesh Tanuku On Wed, May 29, 2024 at 12:53 PM Mukesh Tanuku wrote: > Thanks Bo for your response to my em