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 1u5IA8-00FOS1-9j for pgsql-admin@arkaria.postgresql.org; Thu, 17 Apr 2025 05:51:48 +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 1u5IA5-00FhKo-RP for pgsql-admin@arkaria.postgresql.org; Thu, 17 Apr 2025 05:51:46 +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 1u5IA5-00FhKg-F4 for pgsql-admin@lists.postgresql.org; Thu, 17 Apr 2025 05:51:46 +0000 Received: from mail-ej1-x62e.google.com ([2a00:1450:4864:20::62e]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1u5IA4-000Uag-0c for pgsql-admin@postgresql.org; Thu, 17 Apr 2025 05:51:45 +0000 Received: by mail-ej1-x62e.google.com with SMTP id a640c23a62f3a-ac41514a734so53530366b.2 for ; Wed, 16 Apr 2025 22:51:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1744869103; x=1745473903; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=rVZVx9Oy8ez+ZZT1QMR4WcQX8Fnml9UxKxkymIa1WVA=; b=XkYnCmgQC6Uj5JDP7Jug9UbuQaqCH2GDuvAHbVNAkey/IFnpi3pRS8InG2e6p1ksPJ 1ZnGl04QIGNhsXN58iGsQKpvAkIx3y5OuEDOvjZ7VVvfWGo7S0rv98mgS1OuSRJiKL+t u7R9bOnoU2pOTVSCEi60rBurGB8lAEdQ6ahObXrjkULRf9cfwIGnI6g/Q1onk/dSyKfs F7fvdmyFilwnAaBTmlMupqURcf2BAR5uexTVylae99ShiD+j4oSB0cwxLVj1deUu/i4d 5kTQX3qDOHbzZJuCA1w6ftLayLzU0xdz4gfu1mDK1nvADWTmKD+M/wlbzxCYQZ0Zp2Ot jS0w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1744869103; x=1745473903; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=rVZVx9Oy8ez+ZZT1QMR4WcQX8Fnml9UxKxkymIa1WVA=; b=nd6GfCMx615f8WKjf5JYJSzxdjeGQSEjKujGjhx/QUiznPgT21NWsRn8IMqrzFFuCd Bzv9tJ5UtXLMGlvepX4r3FEsF5eawMcCfa2dyjSNILK+sygjKJE4BJ5W141jYqY1jPRK dYvkdCJICzHS2AuU77P7PT6lHh7DDYuL861eWrShuvz+OUYp9DZ2KUUAkzG/wKP7Luu8 6rPNVRWR1IqknQ0qG2GdVzO4PnF7V15b6NdhPJNWwsGFiRZJRWzaLm9jv8LSi2TQcyBI hXYRHq+Pb0ZgQDBlSKeljxSk/DBW17MsigUCMA1x/aWY8rVW70jTJ2RN6+w1P3cgoaXy ys+w== X-Forwarded-Encrypted: i=1; AJvYcCVApw1FNGgMa7WOrQHOwsVnwbFPAG0xedzgu09KQxxd2QAhWEWvHSputwK52aZL5bjEAyCMn9VXYBP0Ow==@postgresql.org X-Gm-Message-State: AOJu0YySzD39/bOYqaaP9obM7N9a0DFcbsafbJzfKFsApfxG42GUpqoA UTG0y+v6TM6jPez/G32lAvYlCoXDWaEP6H+VwjIsJ8o7WQOTVsUj2AFMRzvAVjH4C/MhSpyMQCv XafG/MJkKaZ67PKWRZjBhAI9dER9ZX5BF X-Gm-Gg: ASbGncupNoUY3LZO0RiKJHsHOPbdVUyhWWpYjlT7yjJO50h/t7kLUcwffTDcgTlXNkk YWCqUqD4m02SEv89h8aDNOvNSEiCxlGdc3Fa4VeIahXAdBONRM7Qwyk3e2nPbByGU6NUj4AtYzu l63tfkJMRrSfW7J77DgVeN0js= X-Google-Smtp-Source: AGHT+IH+oLvvfebeqlzyUGQesOymLPV5IqY1HP8c4bmf4hOY4GHTLISp6a71yvxHZEGtil5R6QG/Zf+boCZF+134QMc= X-Received: by 2002:a17:906:443:b0:ac7:150b:57b2 with SMTP id a640c23a62f3a-acb42aed3e8mr367717166b.41.1744869102855; Wed, 16 Apr 2025 22:51:42 -0700 (PDT) MIME-Version: 1.0 From: Wasim Devale Date: Thu, 17 Apr 2025 11:21:30 +0530 X-Gm-Features: ATxdqUH6EBgiJL-LXGPV3NFhAFcRTGD4bZDKclEJ29cJYfxEJBqgwD4SPzLbYpU Message-ID: Subject: Replication lag To: Pgsql-admin , pgsql-admin Content-Type: multipart/alternative; boundary="0000000000000e2d710632f2ffe2" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000000e2d710632f2ffe2 Content-Type: text/plain; charset="UTF-8" Hi everyone, We have a setup of primary and replica database. We are using the replica as read only purpose. But the queries are long running queries that takes 30 minutes to complete. Do we have any settings in place that will not show replication lag and the queries also executes on replica database without competition on WAL reply? The settings: Hot standby is off And maximum streaming delay is set to -1 Thanks, Wasim --0000000000000e2d710632f2ffe2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi everyone,

We have a setup of primary and replica database. We are using the replica = as read only purpose. But the queries are long running queries that takes 3= 0 minutes to complete.

D= o we have any settings in place that will not show replication lag and the = queries also executes on replica database without competition on WAL reply?=

The settings:
Hot standby is off
And maximum streami= ng delay is set to -1

Th= anks,
Wasim=C2=A0
--0000000000000e2d710632f2ffe2--