From: | yudhi s <learnerdatabase99(at)gmail(dot)com> |
---|---|
To: | Juan Rodrigo Alejandro Burgos Mella <rodrigoburgosmella(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Controlling resource utilization |
Date: | 2024-04-16 20:18:39 |
Message-ID: | CAEzWdqcHxchRxcAYr_OQaVbYOfAEqOCgshGuydf0LmLBe0waZQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 17 Apr, 2024, 1:32 am Juan Rodrigo Alejandro Burgos Mella, <
rodrigoburgosmella(at)gmail(dot)com> wrote:
> Yes sir
>
> SET statement_timeout TO '<milliseconds>'
>
> Atte
> JRBM
>
> El mar, 16 abr 2024 a las 14:46, yudhi s (<learnerdatabase99(at)gmail(dot)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.
>
>>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2024-04-16 20:23:06 | Re: Question on trigger |
Previous Message | Juan Rodrigo Alejandro Burgos Mella | 2024-04-16 20:02:08 | Re: Controlling resource utilization |