| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Danish Hajwane <dane(dot)hajs(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Cc: | دانش حجواني <dane(dot)haj(at)gmail(dot)com> |
| Subject: | Re: MError after replication in postgresql |
| Date: | 2024-09-25 10:44:23 |
| Message-ID: | f25624c2d4a79096cdbd0fbe7771bbe7e26baf89.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 2024-09-25 at 10:57 +0530, Danish Hajwane wrote:
> We are getting error after doing replication on posrgresql 16.3 (OS is HP UX)
> error is regarding Libpq library, we are unable to start sync getting error
>
> FATAL: could not connect to the primary server : libpq is incorrectly linked to backend functions.
> LOG: waiting for WAL to become available at 0/36000018.
That means that there was a problem dynamically loading the
PostgreSQL client library into the server.
This depends a lot on how you built PostgreSQL, what operating system
you have and so on. You didn't tell us anything about these details.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2024-09-25 14:42:07 | Re: Logical Replication Delay |
| Previous Message | Paul Foerster | 2024-09-25 07:16:20 | Re: glibc updarte 2.31 to 2.38 |