> De: "yudhi" <[email protected]> > À: "gparc" <[email protected]> > Cc: "Juan Rodrigo Alejandro Burgos Mella" <[email protected]>, > "pgsql-general" <[email protected]> > Envoyé: Mercredi 17 Avril 2024 09:42:49 > Objet: Re: Controlling resource utilization
> On Wed, 17 Apr, 2024, 12:40 pm , < [ mailto:[email protected] | [email protected] ] > > wrote: >>> De: "Juan Rodrigo Alejandro Burgos Mella" < [ >>> mailto:[email protected] | [email protected] ] > >>> À: "yudhi s" < [ mailto:[email protected] | >>> [email protected] ] > >>> Cc: "pgsql-general" < [ mailto:[email protected] | >>> [email protected] ] > >>> 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? To verify the setting, you can use this command in psql : \drds <your-username> Concerning system resources like CPUs it's not possible. You can use pg_settings view to see which setting you can change and in which context : [ https://www.postgresql.org/docs/current/view-pg-settings.html | https://www.postgresql.org/docs/current/view-pg-settings.html ] Regards Gilles
