public inbox for [email protected]  

help / color / mirror / Atom feed

Controlling resource utilization
3+ messages / 2 participants
[nested] [flat]

* Controlling resource utilization
@ 2024-04-16 19:45  yudhi s <[email protected]>
  0 siblings, 1 reply; 3+ messages in thread

From: yudhi s @ 2024-04-16 19:45 UTC (permalink / raw)
  To: pgsql-general <[email protected]>

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


^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Controlling resource utilization
@ 2024-04-16 20:02  Juan Rodrigo Alejandro Burgos Mella <[email protected]>
  parent: yudhi s <[email protected]>
  0 siblings, 1 reply; 3+ messages in thread

From: Juan Rodrigo Alejandro Burgos Mella @ 2024-04-16 20:02 UTC (permalink / raw)
  To: yudhi s <[email protected]>; +Cc: pgsql-general <[email protected]>

Yes sir

SET statement_timeout TO '<milliseconds>'

Atte
JRBM

El mar, 16 abr 2024 a las 14:46, yudhi s (<[email protected]>)
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
>
>


^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Controlling resource utilization
@ 2024-04-16 20:18  yudhi s <[email protected]>
  parent: Juan Rodrigo Alejandro Burgos Mella <[email protected]>
  0 siblings, 0 replies; 3+ messages in thread

From: yudhi s @ 2024-04-16 20:18 UTC (permalink / raw)
  To: Juan Rodrigo Alejandro Burgos Mella <[email protected]>; +Cc: pgsql-general <[email protected]>

On Wed, 17 Apr, 2024, 1:32 am Juan Rodrigo Alejandro Burgos Mella, <
[email protected]> wrote:

> Yes sir
>
> SET statement_timeout TO '<milliseconds>'
>
> Atte
> JRBM
>
> El mar, 16 abr 2024 a las 14:46, yudhi s (<[email protected]>)
> 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.

>
>>


^ permalink  raw  reply  [nested|flat] 3+ messages in thread

end of thread, other threads:[~2024-04-16 20:18 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-04-16 19:45 Controlling resource utilization yudhi s <[email protected]>
2024-04-16 20:02 ` Juan Rodrigo Alejandro Burgos Mella <[email protected]>
2024-04-16 20:18   ` yudhi s <[email protected]>

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox