Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1stfHG-000cjw-7E for pgsql-general@arkaria.postgresql.org; Thu, 26 Sep 2024 03:34:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1stfHF-0014m8-I1 for pgsql-general@arkaria.postgresql.org; Thu, 26 Sep 2024 03:34:49 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1stfHF-0014m0-0j for pgsql-general@lists.postgresql.org; Thu, 26 Sep 2024 03:34:49 +0000 Received: from mail-pj1-x1034.google.com ([2607:f8b0:4864:20::1034]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1stfH6-0017wA-LB for pgsql-general@postgresql.org; Thu, 26 Sep 2024 03:34:48 +0000 Received: by mail-pj1-x1034.google.com with SMTP id 98e67ed59e1d1-2da4ea59658so474872a91.0 for ; Wed, 25 Sep 2024 20:34:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bitnine-net.20230601.gappssmtp.com; s=20230601; t=1727321679; x=1727926479; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=c1WOZOwuYB1Yo5DKhI9duyK7hdBF/8o/2I9ikLczMJk=; b=stwEp3O+BDBekBFmtsrTypcHeJTGYS2txoUjMKTomQ8JL9rrElMVUixypnN0BBrmML SqJ0dr7HdM3S4CwB+1FvfI7LIhpLCpfi6cCHZChUNh+WJZQMUyor9O61BYSskSZ9O1ne vhNV11xKhpJUK/9ynJ2gjSyy4sc7Vl/+7/8BVbQpI+wXiB2NdrVTjpSJWr0o7GFczDev pzkGH/UQW6Y6jTIUqRRB93jbcITnr0CYJ9PyzcDIQqR98xU2AIFfmeCqxhXB70gVP+PV ZsaWpNKFHDkosG2JWXGyZfA1ZAlV+xLJOlrlY5fML8hgQb82WUbMVoviY5AVywy1k4x1 G6WA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727321679; x=1727926479; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=c1WOZOwuYB1Yo5DKhI9duyK7hdBF/8o/2I9ikLczMJk=; b=MA5iJl1Y8mH9FtUnPxhjp7IBvR7AumSskEaBP5305vIP7OKrMxB5GGvumG/1syqf7Q kIt55tx71HtTW8vqVeNurYOs0NpOW1vn2+B5kSKb+OBC29OIfC7UDL99zXiJaPgHkT5d 9CIHE9xidQiny0miPT9qj8orDQl+8hziaqiZ7Ky8lzSpFnKZceHGv6h8Qez7aczv3MF1 tDqmXQd/GOgGDvxUSjdY3TS4614yosMOf5lXgDXqEVvDxrDqMCcpZD2ta9jRCwDGMxfQ YhTcImZl4wJzjIjULY14AyY2puhNxBDcvdAlNkq11mzr1R+5XF7uBq5mADCxo5RmOfU3 hrCA== X-Gm-Message-State: AOJu0Yz/rJ6ar86G6XNyIWz79OFHsP5sNW3f7aA/UAiYszkjsmAI7pbZ OOJV95tP1nSUAcVGChwaTED1A9XKg+j+ZwNrmUtukdWi1hO0JiRS3n6/FW64o5L522MWs0be62U UFAtO6T7F1bJRIJv7fkLa3Z6FgxI26pF5bDAxjA== X-Google-Smtp-Source: AGHT+IG0QsZKoKRpwG4jnBFHXD3zGbDix6oILki7HGKL/DLBOC5EZkyzM5upinfLwIuQ9pOi+Z+LPxM2r30JwgCwl4A= X-Received: by 2002:a17:90b:1651:b0:2d8:8ab3:2889 with SMTP id 98e67ed59e1d1-2e06ae53a33mr5544096a91.11.1727321679380; Wed, 25 Sep 2024 20:34:39 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Muhammad Usman Khan Date: Thu, 26 Sep 2024 08:34:27 +0500 Message-ID: Subject: Re: MError after replication in postgresql To: Danish Hajwane Cc: pgsql-general@postgresql.org, =?UTF-8?B?2K/Yp9mG2LQg2K3YrNmI2KfZhtmK?= Content-Type: multipart/alternative; boundary="0000000000001cde780622fd6bb4" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000001cde780622fd6bb4 Content-Type: text/plain; charset="UTF-8" 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 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 > --0000000000001cde780622fd6bb4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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=3D/pa= th/to/pgsql/lib:$LD_LIBRARY_PATH

On Wed, 25 Sept= 2024 at 10:35, Danish Hajwane <d= ane.hajs@gmail.com> wrote:

Hi Team,
<= div class=3D"gmail_quote">

We are getti= ng error after doing replication on posrgresql 16.3 (OS is HP UX)
error is regarding Libpq library, we are unable to start sync getting erro= r

FATAL: could not connect to the primary server := libpq is incorrectly linked to backend functions.
LOG: waiting f= or WAL to become available at 0/36000018.

Regards<= /div>
Danish
--0000000000001cde780622fd6bb4--