Re: Controlling resource utilization - Mailing list pgsql-general

From yudhi s
Subject Re: Controlling resource utilization
Date
Msg-id CAEzWdqdJzxUjotQYPpN-6zropJ3e9gMHYOxvtunjJaQj5H1FQA@mail.gmail.com
Whole thread Raw
In response to Re: Controlling resource utilization  (gparc@free.fr)
Responses Re: Controlling resource utilization  (gparc@free.fr)
List pgsql-general

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



De: "Juan Rodrigo Alejandro Burgos Mella" <rodrigoburgosmella@gmail.com>
À: "yudhi s" <learnerdatabase99@gmail.com>
Cc: "pgsql-general" <pgsql-general@lists.postgresql.org>
Envoyé: Mardi 16 Avril 2024 22:29:35
Objet: Re: Controlling resource utilization
ALTER ROLE <your-username> SET statement_timeout = '<time_unit>';
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? 

pgsql-general by date:

Previous
From: gparc@free.fr
Date:
Subject: Re: Controlling resource utilization
Next
From: gparc@free.fr
Date:
Subject: Re: Controlling resource utilization