| From: | Muhammad Usman Khan <usman(dot)k(at)bitnine(dot)net> |
|---|---|
| To: | Danish Hajwane <dane(dot)hajs(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org, دانش حجواني <dane(dot)haj(at)gmail(dot)com> |
| Subject: | Re: MError after replication in postgresql |
| Date: | 2024-09-26 03:34:27 |
| Message-ID: | CAPnRvGsCqEYSh9UQm4MLdwEzXa4+aF4Y3EPZdAB+1RgFpb9hSQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
There are many causes of this issue. One possible solution to handle this
issue is to make sure that proper dynamic linking as follows:
export LD_LIBRARY_PATH=/path/to/pgsql/lib:$LD_LIBRARY_PATH
On Wed, 25 Sept 2024 at 10:35, Danish Hajwane <dane(dot)hajs(at)gmail(dot)com> wrote:
>
> Hi Team,
>
> 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.
>
> Regards
> Danish
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michał Kłeczek | 2024-09-26 07:58:18 | Partitionwise aggregate and runtime partition pruning |
| Previous Message | Tom Lane | 2024-09-25 22:09:44 | Re: Repeatable Read Isolation Level "transaction start time" |