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 1sA7pA-007huA-Sr for pgsql-general@arkaria.postgresql.org; Thu, 23 May 2024 12:45:38 +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 1sA7pA-00C3bh-VE for pgsql-general@arkaria.postgresql.org; Thu, 23 May 2024 12:45:36 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sA7pA-00C3Yg-Js for pgsql-general@lists.postgresql.org; Thu, 23 May 2024 12:45:36 +0000 Received: from mail-vk1-xa2d.google.com ([2607:f8b0:4864:20::a2d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sA7p3-001cay-VR for pgsql-general@lists.postgresql.org; Thu, 23 May 2024 12:45:35 +0000 Received: by mail-vk1-xa2d.google.com with SMTP id 71dfb90a1353d-4df2fcafc19so821391e0c.0 for ; Thu, 23 May 2024 05:45:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1716468329; x=1717073129; darn=lists.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=FJD8GG+948VR5qamuxo82SRDVn1LPGzHNq5/aAJT2aE=; b=IYFvd/7B5ZeOpz4zx6yeUBmzsyRSxx6p25CZVPWWVuHVxIUt6bWG6Bw/lUzl6GKBsk FQ1ynwPFtoiI98Uq/pL6jjl1ZOURK9j3mhVRcgwgeJBCLs4cpZqW0Y3yBbVqkKsbkrtQ mU6HjsCnTzlL4HcSgX9aSKJFqPNzlm0ljw693v2wGfrVQY1pWUDWNoAOSrjZ4KDQ8Ski Ijbq7yFVz1Ywov/mhlp8FYUfGs4jeA3zayYbXx4oe0zxT/8oYZ1rmCZ17jC4Q8FEe3n9 ivjvmARMMcuycv8ObsMXd1Fzg99KE51m8tGIB7qLZSvoAaQ6g1vo/686JMtpSm5VAFs7 F7Rw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716468329; x=1717073129; 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=FJD8GG+948VR5qamuxo82SRDVn1LPGzHNq5/aAJT2aE=; b=UfIB9AqqPZ5j1NsSYiYulmISOxbmHepDk99SPlHyR8QGJhioYCHfMQB2tbBTrVIkNc IoOOllx7rsfS94cDfsn2MIeAMYk3iF12yXM3PtC1qdKiGmP/Ig7X5gwh0wX5bmUlKJeh k3wIZZtXPt4sTGV0KsD7p+DfDf0P7vYJ8O27xLvPysOsDW9x9uUkToZR+xY1POefHTFK Y5f+sTEEKoG+e/sPy03E5b8vm1COtY8HY8IxynaYsYl4Ha6WqBDFb7wyLGgn/ZXn9avG 0U43i4ldGDb6HHMLVvOnqxGd4G5BzMlUidC775+6USnrJOEx0RQn7hzPYAdP0+ZxCKm4 lJXg== X-Gm-Message-State: AOJu0YwyVxV+R1Tr24N25rHpwTNb99cWhqbfbL/Pr/LmRj9a9X21v9SH kGmWjAbvNmm/oh1Y0THDams6UEBckqQsVBNCzXdctsbZfpmHMspn8Ec2Ti+k1AvCX6W950/0ljj Eywz53kYaLkukSRcicCbzCCytdho= X-Google-Smtp-Source: AGHT+IEfZXDhFCHshVtv0bQb5RVGXlXy2CaHLsVM0yOp4vi4gTkrIYzB6MgXYOn8aNF8j6fhKjLPwBB0GICHYFsW58c= X-Received: by 2002:a05:6122:31a8:b0:4d8:7222:b6da with SMTP id 71dfb90a1353d-4e2184ed83amr5186078e0c.6.1716468328794; Thu, 23 May 2024 05:45:28 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: sud Date: Thu, 23 May 2024 18:15:17 +0530 Message-ID: Subject: Re: Long running query causing XID limit breach To: Laurenz Albe Cc: pgsql-general Content-Type: multipart/alternative; boundary="0000000000000193e706191e6d53" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000000193e706191e6d53 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, May 23, 2024 at 1:45=E2=80=AFPM Laurenz Albe wrote: > > > If a long running query on the standby influences the primary, that means > that > you have "hot_standby_feedback" set to "on". Set it to "off". > > > Will the setting up of "hot_standby_feedback" value to OFF will cause the reader instance to give incorrect query results or unexpected query failure which will be potential inconsistency between the writer and reader instance, as because those XID's can be removed/cleaned by the writer node even if its being read by the reader instance query. And it can have more replication lag. So I'm wondering , if this setup is advisable one? --0000000000000193e706191e6d53 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Thu, May 23, 2024 at 1:45=E2=80=AFPM L= aurenz Albe <laurenz.albe@cy= bertec.at> wrote:


If a long running query on the standby influences the primary, that means t= hat
you have "hot_standby_feedback" set to "on".=C2=A0 Set = it to "off".


Will the setting up of "hot_standby_feedback= " value to OFF will cause the reader instance to give incorrect=C2=A0q= uery results or unexpected query failure which will be potential inconsiste= ncy between the writer and reader instance, as because those XID's can = be removed/cleaned by the writer node even if its being read by the reader = instance query. And it can have more replication lag. So I'm wondering= =C2=A0, if this setup is advisable one?
--0000000000000193e706191e6d53--