> De: "Juan Rodrigo Alejandro Burgos Mella" <rodrigoburgosme...@gmail.com>
> À: "yudhi s" <learnerdatabas...@gmail.com>
> Cc: "pgsql-general" <pgsql-general@lists.postgresql.org>
> Envoyé: Mardi 16 Avril 2024 22:29:35
> Objet: Re: Controlling resource utilization

> In postgreSQL, that can be done at a session level, or at a general level (in
> the postgresql.conf configuration file)

> Atte
> JRBM

> El mar, 16 abr 2024 a las 15:18, yudhi s (< [ 
> mailto:learnerdatabas...@gmail.com
> | learnerdatabas...@gmail.com ] >) escribió:

>> On Wed, 17 Apr, 2024, 1:32 am Juan Rodrigo Alejandro Burgos Mella, < [
>> mailto:rodrigoburgosme...@gmail.com | rodrigoburgosme...@gmail.com ] > wrote:

>>> Yes sir
>>> SET statement_timeout TO '<milliseconds>'

>>> Atte
>>> JRBM

>>> El mar, 16 abr 2024 a las 14:46, yudhi s (< [ 
>>> mailto:learnerdatabas...@gmail.com
>>> | learnerdatabas...@gmail.com ] >) escribió:

>>>> Hi ,
>>>> We want to have controls around the DB resource utilization by the adhoc 
>>>> user
>>>> queries, so that it won't impact the application queries negatively. Its 
>>>> RDS
>>>> postgresql database version 15.4.
>>>> Saw one parameter as statement_timeout which restricts the queries to not 
>>>> run
>>>> after a certain time duration and queries will be automatically
>>>> killed/cancelled. However, I don't see any other options to set this at 
>>>> user
>>>> level, rather it's getting set for all or at session level. So I want to 
>>>> know
>>>> if there exists, anyway to control the database resource utilization 
>>>> specific
>>>> to users?
>>>> Regards
>>>> Yudhi

>> This will set the timeout at session level. However, We want to understand, 
>> if
>> it can be done at user/role level, so that any such adhoc user queries can be
>> auto killed or cancelled after the set time.

Or also at role/user level : 
ALTER ROLE < your - username > SET statement_timeout = '<time_unit>' ; 
Regards 
Gilles 

Reply via email to