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 1sCJDf-004i5V-Lm for pgsql-general@arkaria.postgresql.org; Wed, 29 May 2024 13:19:57 +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 1sCJDe-00FCrT-VD for pgsql-general@arkaria.postgresql.org; Wed, 29 May 2024 13:19:54 +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 1sCJDe-00FCrL-K1 for pgsql-general@lists.postgresql.org; Wed, 29 May 2024 13:19:54 +0000 Received: from mail-lj1-x22e.google.com ([2a00:1450:4864:20::22e]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sCJDb-002WW4-VV for pgsql-general@lists.postgresql.org; Wed, 29 May 2024 13:19:53 +0000 Received: by mail-lj1-x22e.google.com with SMTP id 38308e7fff4ca-2e9819a6327so24459231fa.1 for ; Wed, 29 May 2024 06:19:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1716988790; x=1717593590; 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=Tq5TEz8mxecpqqZ4GKyIpSn8Bohh3ghy5TUny2bc3Ns=; b=fXoRNqwKRn5pvnc0rWrbE7QVHpXwjxHlrfrpf5uSB7eX3UrEENLwxnAtZ1JZdcPk4j LZrJ+ZqsSmt/7yYO2rk0waYT2MDzmUQFVAoPQCIPhjr1cWHcYswJ3HrAkxMK255hCxJb sZz82v7RqIYT2d6DaFf/ndU6HgGSClpcubL9BM+DDxGmNmddP/a3OC1BCrHNRFasjD8A CBWi87i9U2BppNMMsytPXa6AzWgN+5r1rWE/b4jswwjem3PBhwC3RSJneInAhHGLnPHm umqZ7N2p1bAvxai33rwuuy6SYHL+sYxEStNkMXPgywKpmriyyi+eMTZMeYtXzqXVhv/8 FoCQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716988790; x=1717593590; 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=Tq5TEz8mxecpqqZ4GKyIpSn8Bohh3ghy5TUny2bc3Ns=; b=vLg4PqsFnhfffnA2hDe91piCLhJVGYVDsOE6N4RfRmnqcpjD4vIAOhbWXT01Nm9l8i Us3fnudoonZhG1bGv47O32PzV9H3kiBjP3j+GW2DgxZEpJqYsETjG9K5d4J2YXHmgcaG eXG6tKWdF8ILhXLepkHhWZ7l4HRiS8WaSdmPd0vIhvpwgE4OeeKB9P7IEWwecyDyILMx sIMlRd1FmuwupiLofunLnjeJ1ROhhNEp2sjjIPALx4Vb6+HgstmRkxZ5sUtqmUH3hizq BmsvW0N8yy85bVTDXuG+lGuNRuAc4oNqCsEREE4vsZMZBCdCdTMONcZVRZk7w2EGVu2G CpJw== X-Gm-Message-State: AOJu0Yzd2U7akR/itLjj8Xl0wnkc9EQ7pOmN4yVGCnxxcEq+479g932K D5+w4ZnFKd0WJsKKTs6srXBdF56DCf7GO9OtKRVyxaLL044oT3LG0njkwGLCqtrGZoShEiwDZSx lGFyC6SCCFDPkrCG+tXYCqNqewz4= X-Google-Smtp-Source: AGHT+IH1toXFntwgJmz0dpZ2Jj7xWdmyaNOfnSPnFbAT3KYQpwusIA0/NppByRpEIOhryuDt6sBQigmbIXUyQSkirls= X-Received: by 2002:a2e:a782:0:b0:2d8:b2e:7bf3 with SMTP id 38308e7fff4ca-2e95af0dbe6mr108682351fa.0.1716988789990; Wed, 29 May 2024 06:19:49 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Greg Sabino Mullane Date: Wed, 29 May 2024 09:19:10 -0400 Message-ID: Subject: Re: Timeout gets unset on a syntax error. To: "ISHAN CHHANGANI ." Cc: "pgsql-general@lists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000e947210619979a05" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000e947210619979a05 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, May 29, 2024 at 6:29=E2=80=AFAM ISHAN CHHANGANI . < f20200230@hyderabad.bits-pilani.ac.in> wrote: > Is there some code within Postgres that resets/removes the signals in cas= e > a query hits any error? > See the comment and call to disable_all_timeouts() in postgres.c, part of the cleanup-after-exception efforts: https://git.postgresql.org/gitweb/?p=3Dpostgresql.git;a=3Dblob;f=3Dsrc/back= end/tcop/postgres.c#l4356 Cheers, Greg --000000000000e947210619979a05 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, May 29, 2024 at 6:29=E2=80=AFAM I= SHAN CHHANGANI . <f20200230@hyderabad.bits-pilani.ac.in> wrote:

Is there some code within Postg= res that resets/removes the signals in case a query hits any error?<= /p>


See the comment and c= all to disable_all_timeouts() in postgres.c, part of the cleanup-after-exce= ption efforts:



Ch= eers,
Greg

--000000000000e947210619979a05--