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 1sbnhn-001WGQ-H1 for pgsql-admin@arkaria.postgresql.org; Wed, 07 Aug 2024 20:56:23 +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 1sbnhl-00A7lP-OF for pgsql-admin@arkaria.postgresql.org; Wed, 07 Aug 2024 20:56:21 +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 1sbnhl-00A7lG-D5 for pgsql-admin@lists.postgresql.org; Wed, 07 Aug 2024 20:56:21 +0000 Received: from mail-oa1-x34.google.com ([2001:4860:4864:20::34]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sbnhj-003gvp-4c for pgsql-admin@lists.postgresql.org; Wed, 07 Aug 2024 20:56:20 +0000 Received: by mail-oa1-x34.google.com with SMTP id 586e51a60fabf-264988283a3so166131fac.0 for ; Wed, 07 Aug 2024 13:56:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1723064177; x=1723668977; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=pMdSG1syGvQIvbywl8du9B3duwrhwVUC+EbcxJnAOYQ=; b=MM5Rrfu9mFzlwrofHjOmnEuWezCRcjq+1wlH07cXzLfxFX57luodjnTFtJh8zQEA6T G7/CIIZW8XlAUbDUXgo2sp4PY5ABjDJ+qrb3e1Styf7tsFZdMk/GKd5LQXb/kz9KVsKr ldTCZP7ZiKwyhK0n1sVbmDEwm1Of5PEb6seMIo2FSixXG/VO1HQ/h68ZCkGglSzcJo8a eljJ0IJjQ2WF7Qt/ub+nXOcRlLL7zTMQKkExjEIk9CMxSS+3H+I2OIKOQ8Q/jVXui8xk KgpHrT0RlDvm8sXa8MqYxaDw7aTi9wkRX81ZoNpBsYYsVYRL4oqcUBICOF0j2zLpSliT L7ig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723064177; x=1723668977; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=pMdSG1syGvQIvbywl8du9B3duwrhwVUC+EbcxJnAOYQ=; b=n/avLV6NYVqXwEaOY7XcfVX3Lb/Rbp57dKbFFSIZRPmXgts6ywQZiCIRImgf0LxQoS CVniOpyXPbslHCFsbr291d8GLzaFNAVEryFunVbDohsdkKU4YN240FDVJNTvFU4aYb0J iP8Tco/i6PiWYCYVigQbwVbVOGIoQY6t680YDthg8ftDWipmbSWsSwg/15trj8/wbAfN byvvVG4QhhEBBZ1LTyWAlbFh8V3RvTSyRjL1AsM6oc+9Tcl+YNB8VYp4AQ0NF/MFeJ6P 6fsIQrAhP6DNAFBhz9Hf7+zzYHWLpT7qEN2aQgb4uTZH+7xarow+msv8lBgMXZSXgrd6 eIPQ== X-Gm-Message-State: AOJu0YxulL9wKPsKcCNE6B0SHzch+FJufgLE5b41tY0CGrYGblYp6bCL n/3JnXtYd6qD6Ha0EFJEj2KaShnKPWwIo2KipViINH5cqC5AiUsllioOpEsR12TFOO3f0925PkL 0Ul6lF/jcgR12gVh8NkQmhplFJ8BKhd4f X-Google-Smtp-Source: AGHT+IEG2yn8SWUoKYuemV50//XRvRNC3OB1f77RWZYpr/6g7owqGFzQsAYJur0an3NRFTR8J4U8zV3QwxKEH7PcjCs= X-Received: by 2002:a05:6871:3325:b0:261:218:dae with SMTP id 586e51a60fabf-26891ea8f86mr25481415fac.33.1723064177313; Wed, 07 Aug 2024 13:56:17 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a8a:c86:0:b0:557:c384:fb61 with HTTP; Wed, 7 Aug 2024 13:56:16 -0700 (PDT) In-Reply-To: References: From: "David G. Johnston" Date: Wed, 7 Aug 2024 13:56:16 -0700 Message-ID: Subject: Re: Statement_timeout effect on replication user To: Teja Jakkidi Cc: pgsql-admin Content-Type: multipart/alternative; boundary="00000000000036d1d4061f1e24aa" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000036d1d4061f1e24aa Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wednesday, August 7, 2024, Teja Jakkidi wrote= : > > I am trying to set statement_timeout parameter to 1 hour at instance leve= l > due 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 > privilege. Now, if I setup statement_timeout at instance level, will this > affect the replication session as well? > Set it to 10 seconds and see if anything breaks? I would doubt it since replication doesn=E2=80=99t involve SQL statements. David J. --00000000000036d1d4061f1e24aa Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wednesday, August 7, 2024, Teja Jakkidi <teja.jakkidi05@gmail.com> wrote:

I am trying to set statement_timeout parameter to 1 hour at instance level = due to some production issues that we have noticed with long running querie= s.
We also have hot stand by replication setup using a user with replication p= rivilege. Now, if I setup statement_timeout at instance level, will this af= fect the replication session as well?

Set it to 10 seconds and see if anything b= reaks?

I would doubt it since replication doesn=E2= =80=99t involve SQL statements.

David J.

--00000000000036d1d4061f1e24aa--