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 1stKhX-00FNfV-1i for pgsql-general@arkaria.postgresql.org; Wed, 25 Sep 2024 05:36:35 +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 1stKhW-003R0T-9e for pgsql-general@arkaria.postgresql.org; Wed, 25 Sep 2024 05:36:34 +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 1stKYf-003GIm-Vu for pgsql-general@lists.postgresql.org; Wed, 25 Sep 2024 05:27:26 +0000 Received: from mail-qk1-x732.google.com ([2607:f8b0:4864:20::732]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1stKYc-000xnw-1g for pgsql-general@postgresql.org; Wed, 25 Sep 2024 05:27:25 +0000 Received: by mail-qk1-x732.google.com with SMTP id af79cd13be357-7a99fd5beb6so53909485a.0 for ; Tue, 24 Sep 2024 22:27:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1727242042; x=1727846842; 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=86P6QaxgXFBY6np/Mssir0YQr7Dr5jJUpqsl52e6grc=; b=ia058Zag31Mu6/B3PCGzKZR4QIL/wRMfIzb0NPHkyzCRK5rh0p1OvS1ytBZ0ptMtTN 7f8u5YXiHORI41BX52ZO8mFUnmdmOyfSJvBF1Usg7JDHppD7HLbZILe37MBgvhxl0Q5h I4PddGDsxh9XCxt03NSwz/b49X0mnZOcWXikIUQ/VrF+ZAYnvqMICPnuw4Fl38K911Hb JOeAR8RXk3nHpry94QwQ0P/i3LEZqZjtSOAoQ/G9gVJjdMndwApWfrmpCgZUSW84ez4N ryJA7arugrpYhUaVfy5yUMBNaaPYYFLJQeklq9gMX1TTthXReSypCiZNH06KVqMOdkrH pqow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727242042; x=1727846842; 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=86P6QaxgXFBY6np/Mssir0YQr7Dr5jJUpqsl52e6grc=; b=c4XfIGQlDKTGjqJa8zOfPAPI000CcnglVt74dp/n+aES4q/rKkRukraMzB3MlvEBWs k3Hx3OygVjzIs5zu8/FxSJ6UPP4ksrzjipuzZATO1wpZ33Or8fRPYDdTpbwc3cW6lCA7 CUBp4xKleydSl/1AK59Yh6mMgETsUSEG45xdARTuREDkUWyf3NwwYSEm+oOis+A8qgYW vCUrbWxspCdUCvPzUjBTCMcTziRnoSaKr5w7fibgP7Xu4tCGjBEJULiczYLh18lJbT9S aBMlOIbJg8epvkjSKvwY4CTJxld83CJzhwBbOoXemJIA1RnHMOOud2IAF6S6O6WHNuUw zUsw== X-Gm-Message-State: AOJu0Yz4j6dTN6746KeFfq9+riyaNwdViqgBXLL2rFI26+VVHvIl+oz+ CIPsP0nYF3K2ndFwhMdtPcc/Zz62OlJgk8H7mqUN1abtNmziQHdwTRFbtc5e0zMf7fv6KaA8w/g cKb/r6pbWh+r/8enwfnEt4+UOf7xKl+ge X-Google-Smtp-Source: AGHT+IHPVefox5guOQG2ABQkVFaK0MiVJTR4+RbovmZ7o8l7RASbHWgjZCMR/Zj1c4PwWm+tZZJ19y+q/TOeuXR7x54= X-Received: by 2002:a05:6214:3d87:b0:6c5:1a1e:a00 with SMTP id 6a1803df08f44-6cb1dbc3fc1mr29040986d6.14.1727242041867; Tue, 24 Sep 2024 22:27:21 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Danish Hajwane Date: Wed, 25 Sep 2024 10:57:10 +0530 Message-ID: Subject: MError after replication in postgresql To: pgsql-general@postgresql.org Cc: =?UTF-8?B?2K/Yp9mG2LQg2K3YrNmI2KfZhtmK?= Content-Type: multipart/alternative; boundary="00000000000058c26c0622eae0a3" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000058c26c0622eae0a3 Content-Type: text/plain; charset="UTF-8" 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 --00000000000058c26c0622eae0a3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hi Team,

We are getting error after doi= ng replication on posrgresql 16.3 (OS is HP UX)
error is regardin= g Libpq library, we are unable to start sync getting error

FATAL: could not connect to the primary server : libpq is incorrec= tly linked to backend functions.
LOG: waiting for WAL to become a= vailable at 0/36000018.

Regards
Danish
--00000000000058c26c0622eae0a3--