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 1sbnZR-001VPK-Ae for pgsql-admin@arkaria.postgresql.org; Wed, 07 Aug 2024 20:47:45 +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 1sbnZP-009yNq-LY for pgsql-admin@arkaria.postgresql.org; Wed, 07 Aug 2024 20:47:43 +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 1sbnZP-009yN5-9h for pgsql-admin@lists.postgresql.org; Wed, 07 Aug 2024 20:47:43 +0000 Received: from mail-pl1-x634.google.com ([2607:f8b0:4864:20::634]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sbnZM-003gjS-Qt for pgsql-admin@lists.postgresql.org; Wed, 07 Aug 2024 20:47:42 +0000 Received: by mail-pl1-x634.google.com with SMTP id d9443c01a7336-1fc566ac769so3195505ad.1 for ; Wed, 07 Aug 2024 13:47:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1723063658; x=1723668458; darn=lists.postgresql.org; h=to:message-id:subject:date:mime-version:from :content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=X3GYz9inwEF0slIsz2MqOqtIsluyDGX0Y4uqF03onlI=; b=PsoLt/DhQtPz5hldWHvrydwUzAZfmUzusmcDCnSYcpHLX3+g1U5j9SPMog+GDX+yxc pvDuke6Q8fC2BYbEDjNjrbWjZ0H8F18Jbsuh7Rt3PM7LzJW9WD/Jpt5WOF71l3XFOLI7 SlITTX29yfSYQ8JH2aYfH0dMG6Bd+cwBBZz9ZA21MdORKxX+n/p+wuBQG4Wx6BSDREmo lwsQDUBibtDxl/OtS78Rr24Tqcsqng3NXNsrOOQtIBbY5lDNIWIY/XHh6yyj2eC4k+4u tIiYkWpRI5EAZN58zKjlVOYhhTHRRIN88bNw25d44d/iooaY72C7PdY9vKaodZXjtZGP yyqg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723063658; x=1723668458; h=to:message-id:subject:date:mime-version:from :content-transfer-encoding:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=X3GYz9inwEF0slIsz2MqOqtIsluyDGX0Y4uqF03onlI=; b=ex3z49uA7qWSJBawMi3fSbp4dosWvSizs8HxG+drphQjVYQb+gUBRTUkXCRonYUPMH eH89bKwIuwvToqb/MzReZaOPaDmTRwxfh79E09Cum3+DF5khwYdx6ZUWXTPaEeqkFAaj KRnexLJvJ52Nv9Otm/KJct99kj2lmbNFuWkiVjr6B5E0s7mn9gq9wWQtImb4J7D/EMS3 pbmo2ihhl/Bgzeu5f/g3caTdadmsJey1EzssjuGlO/XVFXR834P89luadYm8XWUvI+sG 6sc55jWpvjh2HSG258wSx0DIM1a3h/wCdgxayQZZ/3jN7ZXUWnfVHQbmW1G0WV5J/MtO bBog== X-Gm-Message-State: AOJu0YyeY9p47atNFWh/qay39GTDEcxRt6zeNAAuvpGURTujZqWM8hCg VjYPJI2SRVFUaJbLDpCvKQihPbuQKrmt4Kgy6Rd5cuxftthxg+M3EsXURA== X-Google-Smtp-Source: AGHT+IEwsGfFUzK1ZXoQSVbiAHUQuiMRgfmIoiTTf/zBN6AdUs1WHqoNVMmEs1qdfbXw5LZPOppfDA== X-Received: by 2002:a17:902:ce86:b0:1fd:a043:e3fb with SMTP id d9443c01a7336-1ff574e385dmr191336525ad.63.1723063657876; Wed, 07 Aug 2024 13:47:37 -0700 (PDT) Received: from smtpclient.apple ([208.28.126.37]) by smtp.gmail.com with ESMTPSA id d9443c01a7336-1ff592b6915sm110541545ad.305.2024.08.07.13.47.37 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 07 Aug 2024 13:47:37 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable From: Teja Jakkidi Mime-Version: 1.0 (1.0) Date: Wed, 7 Aug 2024 13:47:26 -0700 Subject: Statement_timeout effect on replication user Message-Id: To: pgsql-admin X-Mailer: iPhone Mail (21F90) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hello Postgres Admins, I am trying to set statement_timeout parameter to 1 hour at instance level d= ue to some production issues that we have noticed with long running queries.= We also have hot stand by replication setup using a user with replication pr= ivilege. Now, if I setup statement_timeout at instance level, will this affe= ct the replication session as well? Thanks, J. Teja.=