Libpq library error when doing physical Replication
Hi Team,
I Have installed postgresql 16.4 &16.3 on HP UX B.11.31 U ia64.
Installation is successful but when i am doing physical replication i m
getting Libpq error and sync not starting, unable to connect to primary
server. Kindly check the screenshot below
Regards
Danish
Attachments:
A1F4A98A-C2D7-4432-983C-11DC55051CED.pngimage/png; name=A1F4A98A-C2D7-4432-983C-11DC55051CED.pngDownload+39-30
Hi Danish,
I Have installed postgresql 16.4 &16.3 on HP UX B.11.31 U ia64. Installation is successful but when i am doing physical replication i m getting Libpq error and sync not starting, unable to connect to primary server. Kindly check the screenshot below
HP UX support was dropped in PG16 according to the release notes [1]https://www.postgresql.org/docs/release/16.0/:
Remove support for HP-UX (Thomas Munro)
I'm afraid you will have to ask for help somebody who provided this
build for you.
[1]: https://www.postgresql.org/docs/release/16.0/
--
Best regards,
Aleksander Alekseev
Hi Aleksander
I have tried on version 12 of PostgreSQL getting same error
Regards
Danish
On Thu, 14 Nov 2024 at 7:22 PM, Aleksander Alekseev <
aleksander@timescale.com> wrote:
Show quoted text
Hi Danish,
I Have installed postgresql 16.4 &16.3 on HP UX B.11.31 U ia64.
Installation is successful but when i am doing physical replication i m
getting Libpq error and sync not starting, unable to connect to primary
server. Kindly check the screenshot belowHP UX support was dropped in PG16 according to the release notes [1]:
Remove support for HP-UX (Thomas Munro)
I'm afraid you will have to ask for help somebody who provided this
build for you.[1]: https://www.postgresql.org/docs/release/16.0/
--
Best regards,
Aleksander Alekseev
Hi Danish,
I have tried on version 12 of PostgreSQL getting same error
As of today PG12 is end-of-life and will no longer receive bug fixes [1]https://www.postgresql.org/about/news/postgresql-171-165-159-1414-1317-and-1221-released-2955/.
Does the issue reproduce with PG13, 14 or 15?
[1]: https://www.postgresql.org/about/news/postgresql-171-165-159-1414-1317-and-1221-released-2955/
--
Best regards,
Aleksander Alekseev
Hi Aleksander
Tried on PostgreSQL 15 also same error
Regards
Danish
On Thu, 14 Nov 2024 at 11:39 PM, Aleksander Alekseev <
aleksander@timescale.com> wrote:
Show quoted text
Hi Danish,
I have tried on version 12 of PostgreSQL getting same error
As of today PG12 is end-of-life and will no longer receive bug fixes [1].
Does the issue reproduce with PG13, 14 or 15?
[1]:
https://www.postgresql.org/about/news/postgresql-171-165-159-1414-1317-and-1221-released-2955/--
Best regards,
Aleksander Alekseev
Hi Danish,
Tried on PostgreSQL 15 also same error
We are going to need more information than this since most of us don't
have access to HP-UX (I certainly don't). The exact steps to reproduce
the issue in a clean HP-UX environment (commands you execute in bash)
and the exact PostgreSQL & libpq versions would be a good starting
point.
--
Best regards,
Aleksander Alekseev