| From: | Kashif Zeeshan <kashi(dot)zeeshan(at)gmail(dot)com> |
|---|---|
| To: | vijay patil <vijay(dot)postgres(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Pgpool with high availability |
| Date: | 2024-05-28 16:54:22 |
| Message-ID: | CAAPsdheb+Vax_s15Y2-+Z3prSXWuAbMUUmhU0P90Qafk=x1VuA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi Vijay
Can you please share the error log, as from the description its hard to
figure out the issue causing this problem.
Regards
Kashif Zeeshan
Bitnine Global
On Tue, May 28, 2024 at 9:42 PM vijay patil <vijay(dot)postgres(at)gmail(dot)com>
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.
>
> I'm seeking assistance to address this issue. My setup consists of three
> nodes, each hosting both PostgreSQL and Pgpool services."
>
>
> Thanks
>
> Vijay
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Francisco Olarte | 2024-05-28 17:14:49 | Re: Memory issues with PostgreSQL 15 |
| Previous Message | David G. Johnston | 2024-05-28 13:43:07 | Re: Use of inefficient index in the presence of dead tuples |