MIME-Version: 1.0
References: <E970973D-C336-4EA5-91FD-58E4DBF9DFFB@gmail.com>
 <CAKFQuwZH5H=U3RqBn9AEsXOgyY12LHZZpJbCd_j0Q=N4zw5GaA@mail.gmail.com>
In-Reply-To: 
 <CAKFQuwZH5H=U3RqBn9AEsXOgyY12LHZZpJbCd_j0Q=N4zw5GaA@mail.gmail.com>
From: Muhammad Imtiaz <imtiazpg712@gmail.com>
Date: Thu, 8 Aug 2024 13:43:34 +0500
Message-ID: 
 <CACW1Ly0reU+PYtn8adDNuhhXcC=FLjbYdBfnor9wCEf3gdZpmw@mail.gmail.com>
Subject: Re: Statement_timeout effect on replication user
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: Teja Jakkidi <teja.jakkidi05@gmail.com>,
	pgsql-admin <pgsql-admin@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="00000000000041b51b061f280628"
Archived-At: 
 <https://www.postgresql.org/message-id/CACW1Ly0reU%2BPYtn8adDNuhhXcC%3DFLjbYdBfnor9wCEf3gdZpmw%40mail.gmail.com>
Precedence: bulk

--00000000000041b51b061f280628
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi,

Setting statement_timeout to 1 hour means that any query running longer
than 1 hour will be automatically stopped. This applies to queries from
applications or users, including those with replication privileges.
However, this timeout does not affect the replication process itself. The
continuous transfer of WAL files from the primary server to replicas will
continue as usual, unaffected by the statement_timeout setting.

Regards,
Muhammad Imtiaz

On Thu, Aug 8, 2024 at 1:56=E2=80=AFAM David G. Johnston <david.g.johnston@=
gmail.com>
wrote:

> 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 runni=
ng
>> queries.
>> We also have hot stand by replication setup using a user with replicatio=
n
>> privilege. Now, if I setup statement_timeout at instance level, will thi=
s
>> 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.
>
>

--00000000000041b51b061f280628
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<br><br>Setting statement_timeout to 1 hour means that =
any query running longer than 1 hour will be automatically stopped. This ap=
plies to queries from applications or users, including those with replicati=
on privileges. However, this timeout does not affect the replication proces=
s itself. The continuous transfer of WAL files from the primary server to r=
eplicas will continue as usual, unaffected by the statement_timeout setting=
.<br><br>Regards,<br>Muhammad Imtiaz</div><br><div class=3D"gmail_quote"><d=
iv dir=3D"ltr" class=3D"gmail_attr">On Thu, Aug 8, 2024 at 1:56=E2=80=AFAM =
David G. Johnston &lt;<a href=3D"mailto:david.g.johnston@gmail.com">david.g=
.johnston@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex">On Wednesday, August 7, 2024, Teja Jakkidi &lt;<a href=
=3D"mailto:teja.jakkidi05@gmail.com" target=3D"_blank">teja.jakkidi05@gmail=
.com</a>&gt; wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><b=
r>
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.<br>
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?<br>
</blockquote><div><br></div><div>Set it to 10 seconds and see if anything b=
reaks?</div><div><br></div><div>I would doubt it since replication doesn=E2=
=80=99t involve SQL statements.</div><div><br></div><div>David J.</div><div=
><br></div>
</blockquote></div>

--00000000000041b51b061f280628--