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 1rwzwg-005luu-8K for pgsql-general@arkaria.postgresql.org; Wed, 17 Apr 2024 07:43:06 +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 1rwzwe-009Wyp-U9 for pgsql-general@arkaria.postgresql.org; Wed, 17 Apr 2024 07:43:04 +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 1rwzwe-009Wyh-Jh for pgsql-general@lists.postgresql.org; Wed, 17 Apr 2024 07:43:04 +0000 Received: from mail-qk1-x72e.google.com ([2607:f8b0:4864:20::72e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rwzwc-001Pqs-9Z for pgsql-general@lists.postgresql.org; Wed, 17 Apr 2024 07:43:03 +0000 Received: by mail-qk1-x72e.google.com with SMTP id af79cd13be357-78ecd752a7cso324896385a.0 for ; Wed, 17 Apr 2024 00:43:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713339780; x=1713944580; 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=FIk0Gp/ePZyEHngtlbQlSlxpe459EQRZg9NHKJrlX9g=; b=fl/8EUs2GQEp1m8PfZSnBZvAphAugCdW8c8AKG5i7mANNnNjgKvQrxucsoO4vBGFnq QFgiqppX0ZbAZsuCz1gQBzwtotifOdB2UzVzgJMjEvDcOrTJtbJ+6K98fmRmqKPZ698e igu/EbtoklxXhmWDVGn0yJHFMr5ck17ga8qaGIpd6CwJJxGaO6mMt8WHoJsCDBQHbe+q EVA6CKZj92zfRJU55yjpLpwa35spYEKVsJUCtkCPUTpjYfriPHvYZDJ38m9JA8KY4VUc kRZML+/BJtl6J1qugH9YvTtfQ5FZJa+WAGeqjXGqTQlpeq35Cy3xVYz+N5lxQRqRQLSl f15w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713339780; x=1713944580; 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=FIk0Gp/ePZyEHngtlbQlSlxpe459EQRZg9NHKJrlX9g=; b=YV1IuFtgm/JWcZgCob2UmFmozrGvsVAS78Wmfo5Wwl1w16xv0b+2xggAjdyUEi/CEs bbP6XHHjI+/hjocA7BHtlsJjdCbGh8c5Zy77akj3jb4xX0zQll6lWPN8UJUX0Ub2UccQ IsyVQPCHS2W7GsPdWgZT64wm1vy+XeEYyiNvm5E+KGXR3Z8jzBBDlulcwr3DAj5vwnuD KHcI4Xghg4ue8n7IV2RmRBokjXII40tgJoluNZqOitrj6AIanluBjOpB6xbqIs4HswHu YJMicIbVV8ekRr9whXohemz7DMyonpTvs6eAa+/a2OCqxQ9465MpWwYuDJ3R688jiTi8 zGAA== X-Forwarded-Encrypted: i=1; AJvYcCVWrkXppT/AQTsdKK4vm62UfCxl/1UlFDqe7Vkmr/oRp32o33nWiOWAsyDzUaO4EG4o9FBSVni8tu++wyYel2lqABLuOJpD9qdEPCyWkpE9qB0E X-Gm-Message-State: AOJu0YyuC/L1kzg/AIetTrfBCpw7m6zRKvl84wkQqQXr6BBaxmGexYAN 7dCAH9X1SSUQLOxINln+6pHa2Oh1f3wz4eeQyRrT+e+bNr/xCREwvEj7iY7bVHgCO+J2HNAKsHU 8K3puW/rKA8qwUKYpDbWn7F0yBEE= X-Google-Smtp-Source: AGHT+IFPqFZAzfPuBZn46ImpJsfCavnJIj4WsWIo8GaavJv1MieslXd4bxDu/PRevDdzu3BLw2WJe1cD8LLTL/bFzgs= X-Received: by 2002:a05:6214:10e4:b0:69b:5ecb:aef1 with SMTP id q4-20020a05621410e400b0069b5ecbaef1mr13880539qvt.35.1713339780353; Wed, 17 Apr 2024 00:43:00 -0700 (PDT) MIME-Version: 1.0 References: <1024954288.180821153.1713337816069.JavaMail.zimbra@free.fr> In-Reply-To: <1024954288.180821153.1713337816069.JavaMail.zimbra@free.fr> From: yudhi s Date: Wed, 17 Apr 2024 13:12:49 +0530 Message-ID: Subject: Re: Controlling resource utilization To: gparc@free.fr Cc: Juan Rodrigo Alejandro Burgos Mella , pgsql-general Content-Type: multipart/alternative; boundary="000000000000fcd7fc0616460037" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000fcd7fc0616460037 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, 17 Apr, 2024, 12:40 pm , wrote: > > > ------------------------------ > > *De: *"Juan Rodrigo Alejandro Burgos Mella" > *=C3=80: *"yudhi s" > *Cc: *"pgsql-general" > *Envoy=C3=A9: *Mardi 16 Avril 2024 22:29:35 > *Objet: *Re: Controlling resource utilization > > ALTER ROLE SET statement_timeout =3D ''; > > Regards > Gilles > > Thank you so much. That helps. This statement is succeeding for user as I executed. So it's working I believe. But to immediately verify without manually running queries and waiting for it to be auto killed to confirm, Is there any system table which we can verify to see if this setting is effective, as because I don't see any such columns in pg_user or pg_role which shows the statement_timeout. And is there a way to put similar cap/restrictions on other db resources like cpu, memory, I/O at specific user/role level? > --000000000000fcd7fc0616460037 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Wed, 17 Apr, 2024, 12:40 pm , <gparc@free.fr> wrote:


De: "Juan Rodrigo Alejandro Burgos Mella" <rodrigoburgosmella@gmail.com>
=C3=80: "yudhi s= " <learnerdatabase99@gmail.com>
Cc: "= ;pgsql-general" <pgsql-general@lists.postgresql.org= >
Envoy=C3=A9: Mardi 16 Avril 2024 22:29:35
Objet: <= /b>Re: Controlling resource utilization
<=
span>ALTER ROLE <your-username>=
; SET statement_timeout =3D '<=
;time_unit>';
Regards
Gilles



Thank you so much. That helps.=C2=A0
=

This statement is succeeding for us= er as I executed. So it's working I believe.=C2=A0

But to immediately verify without manually r= unning queries and waiting for it to be auto killed to confirm, Is there an= y system table which we can verify to see if this setting is effective, as = because I don't see any such columns in pg_user or pg_role which shows = the statement_timeout.

= =C2=A0And is there a way to put similar cap/restrictions on other db resour= ces like cpu, memory, I/O at specific user/role level?=C2=A0
--000000000000fcd7fc0616460037--