From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | vijay patil <vijay(dot)postgres(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Pgpool with high availability |
Date: | 2024-05-28 18:01:20 |
Message-ID: | 22b7b0b8-c348-44df-a9a4-ceba94f379b2@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 5/28/24 1:31 AM, vijay patil wrote:
>
> HI Team,
>
> "I'm encountering challenges while configuring Pgpool with high
> availability. The initial setup is completed, and Pgpool is operational
> on a single node, functioning without issues. However, upon attempting
> to start Pgpool on any additional nodes, particularly node 2, it becomes
> immediately unreachable.
And how we are supposed to arrive at an answer with essentially no
information provided?
Need:
1) Configuration for initial setup.
2) A more detailed explanation of what "... upon attempting
to start Pgpool on any additional nodes" means? Include configuration
changes.
3) The error messages.
4) Where the nodes are located?
>
> I'm seeking assistance to address this issue. My setup consists of three
> nodes, each hosting both PostgreSQL and Pgpool services."
>
>
> Thanks
>
> Vijay
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | yudhi s | 2024-05-28 20:04:28 | Re: Long running query causing XID limit breach |
Previous Message | Francisco Olarte | 2024-05-28 17:14:49 | Re: Memory issues with PostgreSQL 15 |