Re: Controlling resource utilization

2024-04-17 Thread gparc
> De: "yudhi" > À: "gparc" > Cc: "Juan Rodrigo Alejandro Burgos Mella" , > "pgsql-general" > Envoyé: Mercredi 17 Avril 2024 09:42:49 > Objet: Re: Controlling resource utilization > On Wed, 17 Apr, 2024, 12:40 pm , < [ mailto:g

Re: Controlling resource utilization

2024-04-17 Thread gparc
> De: "Juan Rodrigo Alejandro Burgos Mella" > À: "yudhi s" > Cc: "pgsql-general" > 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) >

Re: Not able to purge partition

2024-03-21 Thread gparc
- Mail original - > De: "Laurenz Albe" > À: "veem v" , "pgsql-general" > > Envoyé: Jeudi 21 Mars 2024 13:48:19 > Objet: Re: Not able to purge partition > On Thu, 2024-03-21 at 11:07 +0530, veem v wrote: >> CREATE TABLE schema1.test_part_drop_parent >> ( >>  c1 varchar(36)  NOT NULL ,

Re: Users and object privileges maintenance

2024-02-19 Thread gparc
On 18.02.2024 15 :19, Dominique Devienne wrote: ... ... But you of course can connect only to DBs you have explicit access to. Just beware that before 15, the built-in PUBLIC role, which all ROLEs are implicitly members of, had implicit access to newly created DBs. It's still the same