Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gjSyQ-0006hm-Ff for pgsql-admin@arkaria.postgresql.org; Tue, 15 Jan 2019 17:58:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gjSyO-0000w1-8n for pgsql-admin@arkaria.postgresql.org; Tue, 15 Jan 2019 17:58:00 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gjSyN-0000mw-Mq for pgsql-admin@lists.postgresql.org; Tue, 15 Jan 2019 17:58:00 +0000 Received: from sonic313-14.consmr.mail.bf2.yahoo.com ([74.6.133.124]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gjSyI-0002Lz-N1 for pgsql-admin@lists.postgresql.org; Tue, 15 Jan 2019 17:57:57 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1547575071; bh=78quHdJl54J5N1J9T4Z8VgsNAkHxlX6ZBYJ8L56rkOA=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=R8xqQk5N/ia3lZ4S3qI7FLnKcshwINIMhB+DHTZIgv7MwlavWGPRWE7gaMI/MFp55yP84ulnwHtZNQ0+Hz+6DfbpEnQ5uXwm9RaY4i3rmm8HpJ8tSz5qv9Ub2OJ663umHHbkJee+z/mdaZNhBbr7vrQ17afmDZ9UeJwtHXsmfmh7+daLHur5g3DnHTtI29iNpJIzmWG8yaRJyq//gfOn2BDtmFIomDWq2KSnN4DIjG2XS8RlVD4TwJEZvFlgqBjU2ep6RG6ZkIv/kEuXc4HNeRjSkrvQhR0twKhs7pMfyXUgQ/UYQeUP0QFiCl8homaTmSG6qkDLW2YDxuFttz5wTw== X-YMail-OSG: CTToo6AVM1mi.m25.SIUxLvNrIW43EyqQ0ecCdct7fyEzKsEkKPlBhyvHFJVix2 WVin88AXrpbozWcFSKykkJ1tZEG_wgcWtIQo6KXe6U5Sa3nEnf0x428u4zG7_Q77I5ez3o4prFnz z4ePSwOadOEihjy02FWd.LDoBarThxBcitnONsrlQUhfhxNNE5q_iGjUdaqC_KHh7aejsu1uWsNd _PGdDGdE_tIh4el15vInDqzM9UZmPJB9aCuvaHrDw0FpkDKlXH9lvuTsyvpHaaKn3r6ndDNutQRj 16CQmLhQ18ANVw8RX1h9YGrYVGd2fy6W04K3Fi22ew_mwnS2AtnBQ8FV_EQMVlPwwZ8IbNVOlPPW .bti31df.sUKynai.LqZFj3DhQoqSJY89g99gE3GJDG02c.4cKx8M7uShKwhXcIKg6bLkCXuD66R 2owGqVRjAtLEqbaoSH.eEagvr3yrcIyEx4i0K7Rp7Kd5MfNn6uHDYXRF_CRzkLHO_P5eFVDMsoZV g0N8lNeIKX_5AKGCI2oIQKtnM1XNmtO1bMkJrc3ifGWV.dR_HAt5xcOAbMOc77RSb.ahNFove0we UD254zQs9XPpdTfRpTfyHmsNnEh8nVSPmPu3RclZ6nNXGPymFopqAGFA9XdZR1CgM9kgY8txrR2w QGUAjyJf.O2EGKSvb8s95D889g15spOkXANBRiuYkTK3qhbZlF.eFX1MbwBYqxT5jD1xxNj41qdK UH5GpkN7qrh7llOpoL2AcZZNjm1.2slKVRqgjnfUUuI8FhP4W7a7Y8aW_4AzxLKFDfvTYJPL8aV9 Bs.pZJ2T16x6Ehru3_QB0AEAzvwDI8CJOjxNUqXxOvsHZQZMg5XklYbgOaMvAVK3xdYCcSbNlimv 6DQB.KW9YNE86GeuJCPpsUQ9A2IH3Jj66_LdY6UwMO8XWvr0YduMWPwvajxPfucEfk9i3mr.WTwZ tNWNMF9TGXXci9.3VMErVISJVPUDBmvnbO3KDceZUHyYvC5Fx1qjOshPeLAY1Hil_GBTqsccp4o3 uLGgXYIKVprEGQVu5e10990xcpzi.Kg1HrL8wGFpvOHQRiFydOc7en76mvJcYIZAFdn_sF9xlcK4 - Received: from sonic.gate.mail.ne1.yahoo.com by sonic313.consmr.mail.bf2.yahoo.com with HTTP; Tue, 15 Jan 2019 17:57:51 +0000 Date: Tue, 15 Jan 2019 17:57:50 +0000 (UTC) From: Pepe TD Vo Reply-To: Pepe TD Vo To: Pepe TD Vo , Thomas Kellerer , "pgsql-admin@lists.postgresql.org" Message-ID: <442357970.589897.1547575070485@mail.yahoo.com> In-Reply-To: <2088852869.450616.1547563351918@mail.yahoo.com> References: <858026322.18309717.1547479488317.ref@mail.yahoo.com> <858026322.18309717.1547479488317@mail.yahoo.com> <298a21d9-c6b3-e80b-adf5-4583c9df2f70@gmx.net> <2088852869.450616.1547563351918@mail.yahoo.com> Subject: Re: create tablespaces and users MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_589896_644419768.1547575070483" X-Mailer: WebService/1.1.12993 YahooMailNeo Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 Content-Length: 13029 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk ------=_Part_589896_644419768.1547575070483 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable In Oracle, we set up each =E2=80=9Cschema=E2=80=9D/user for each developer = and/or each database login. This allowed the schema logon into their own da= tabase and create their own tables/function/triggers, etc....=C2=A0 How do = I avoid all people logon into the postgres db but their own schema/pgsql us= er? thank you. Bach-Nga No one in this world is pure and perfect.=C2=A0 If you avoid people for the= ir mistakes you will be alone. So judge less, love and forgive more.To call= him a dog hardly seems to do him justice though in as much as he had four = legs, a tail, and barked, I admit he was, to all outward appearances. But t= o those who knew him well, he was a perfect gentleman (Hermione Gingold) **Live simply **Love generously **Care deeply **Speak kindly.*** Genuinely = rich *** Faithful talent *** Sharing success=20 On Tuesday, January 15, 2019 9:42 AM, Pepe TD Vo wro= te: =20 so you suggest not to create the tablespace and associate with the databas= e, right?=C2=A0 What's about the owner?=C2=A0 Still postgres or create user= owner?=C2=A0 From Oracle we have 4 schemas for cidr database. CREATE DATABASE "CIDR"=C2=A0 =C2=A0 WITH=C2=A0=C2=A0 =C2=A0 OWNER =3D postg= res=C2=A0 =C2=A0--> or new users????=C2=A0 =C2=A0 ENCODING =3D 'UTF8'=C2=A0= =C2=A0 LC_COLLATE =3D 'en_US.UTF-8'=C2=A0 =C2=A0 LC_CTYPE =3D 'en_US.UTF-8= '=C2=A0 =C2=A0 TABLESPACE =3D pg_default=C2=A0 =C2=A0 CONNECTION LIMIT =3D = -1;=C2=A0thank you. Bach-Nga No one in this world is pure and perfect.=C2=A0 If you avoid people for the= ir mistakes you will be alone. So judge less, love and forgive more.To call= him a dog hardly seems to do him justice though in as much as he had four = legs, a tail, and barked, I admit he was, to all outward appearances. But t= o those who knew him well, he was a perfect gentleman (Hermione Gingold) **Live simply **Love generously **Care deeply **Speak kindly.*** Genuinely = rich *** Faithful talent *** Sharing success=20 On Tuesday, January 15, 2019 2:26 AM, Thomas Kellerer wrote: =20 Pepe TD Vo schrieb am 14.01.2019 um 16:24: > From oracle databases, I have few tablespaces and users created for > that particular database.=C2=A0 How could I do the same for postgres? The question is: what was the reason to use tablespaces in Oracle?=20 Most of the time I see an Oracle installation with a tablespace per user, i= t's to manage space more easily. As Postgres does not store data in one huge file, this is not really releva= nt here.=20 As soon as a table is dropped, the space is released from the filesystem.= =20 So just create the users and let them use the default tablespace, unless yo= u used the tablespaces to distribute the I/O load to different disks.=20 Thomas =20 =20 ------=_Part_589896_644419768.1547575070483 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
In Oracle, we set up each =E2=80=9Cschema=E2= =80=9D/user for each developer and/or each database login. This allowed the= schema logon into their own database and create their own tables/function/= triggers, etc....  How do I avoid all people logon into the postgres d= b but their own schema/pgsql user?

thank = you.

Bach-Nga

No one in this world is pure and perfect.  If you avoid people for t= heir mistakes you will be alone. So judge less, love and forgive more.
To call him a dog hardly seems to do him justice thoug= h in as much as he had four legs, a tail, and barked, I admit he was, to al= l outward appearances. But to those who knew him well, he was a perfect gen= tleman (Hermione Gingold)

**Live simply **Love generously **Care deeply **Speak kindly.
*** Genuinely rich *** Faithful talent *** Sharing success


On Tuesday= , January 15, 2019 9:42 AM, Pepe TD Vo <pepevo@yahoo.com> wrote:
<= /font>


so you suggest not to create the tablespac= e and associate with the database, right?  What's about the owner?&nbs= p; Still postgres or create user owner?  From Oracle we have 4 schemas= for cidr database.

CREATE DATABASE "CIDR"
    WITH 
  &nb= sp; OWNER =3D postgres   --> or new users????
    ENCODING= =3D 'UTF8'
    LC_COLLATE =3D 'en_US.UTF-8'
    LC_CTYPE =3D 'en_U= S.UTF-8'
    TABLESPACE =3D pg_default
    CONNECTION L= IMIT =3D -1;
 
thank you.

Bach-Nga
No one in this world is pure and perfect.  If you = avoid people for their mistakes you will be alone. So judge less, love and = forgive more.
To call him a dog hardly seems to do him justice though = in as much as he had four legs, a tail, and barked, I admit he was, to all = outward appearances. But to those who knew him well, he was a perfect gentl= eman (Hermione Gingold)

**Live simply **Love generously **Care deeply **Speak kindl= y.
*** Genuinely rich= *** Faithful talent *** Sharing success


<= div class=3D"yiv2823704197yahoo_quoted" style=3D"display:block;">
On Tuesday, January 15, 2019 2:26 AM, Thomas Kellerer <spam_= eater@gmx.net> wrote:


Pepe TD Vo schrieb am 14.01.2019 um 16:24:

> Fr= om oracle databases, I have few tablespaces and users created for
> that particular database.  How could I do the same for = postgres?


The question is: what = was the reason to use tablespaces in Oracle?

Most of the time I see an Oracle installation with a tablespace p= er user, it's to manage space more easily.

As Postgres does not store data in one huge file, this is not really r= elevant here.
As soon as a table is dropped, the space i= s released from the filesystem.

So ju= st create the users and let them use the default tablespace, unless you use= d the tablespaces
to distribute the I/O load to different= disks.

Thomas







<= /div>


------=_Part_589896_644419768.1547575070483--