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 1gjPvO-0004C9-Rn for pgsql-admin@arkaria.postgresql.org; Tue, 15 Jan 2019 14:42:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gjPvN-0004vS-9W for pgsql-admin@arkaria.postgresql.org; Tue, 15 Jan 2019 14:42:41 +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 1gjPvN-0004qd-17 for pgsql-admin@lists.postgresql.org; Tue, 15 Jan 2019 14:42:41 +0000 Received: from sonic301-3.consmr.mail.bf2.yahoo.com ([74.6.129.42]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gjPvK-0006Ho-7U for pgsql-admin@lists.postgresql.org; Tue, 15 Jan 2019 14:42:40 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1547563355; bh=kKLmaIt1L6eL1nhK6qWGFAXuurI44L+u1eX/JdvZlMM=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=b3THZilESBFjozP/QfJRxiOZoJInoIMh29Z9SsYzeCNY0Li9rBGjjFlaiS86701CpbqcxODaef0OyOh6XMwR30pPx5L54wYch8hqWv10W3auRe4J8As7hZnYetaGY3OrGJBAos4yydF2TgCkj7zzloAORzxPvfJO59gfc4mqP8ILLH/fINYOrvjnasFE1whVyduA5/BofAKRgoje4dqdkDw7WKrot7mOyP1ulgbF5c6miQnkpMMvWLSUfeNqUd2VP0QL1bAWE81/geerUsYM2PusRvhAu1iZ3YdDZCPWWJtouW8w2dEvwzFHRlzbCbbAao6kgb4HJlQJmM5kobmgSg== X-YMail-OSG: lk.NrZYVM1kWqVxGkA9.6_.ht3hnpUyiDZm2bnlyDAFKUyyDcCdhsrWoqYBpeoN 9hiQejqYKYKfrKgqlzeemKIMpIoEw06ofepd4mQjoFIWJwqAQCNPzrNVlA5dzy0RHtrSLEex75fL e5pw6EaSczN4Dg05CdI.q2EV4kZ_Dy2Q9316pTqJN_RsORyfdLN1_QtuleddMVELa96Jh_K1z_62 w6PKmZyqbCFlG8GsoWKdFANnruRnDCkJiFX27jYdmyhH3HrCgiOu89v.NY3dgYQuCY5_5JP3pScQ M27IYPPNULxjH4V635TAPmC56THKcRdM.7qlBBZuywYcS64Liyalhr8bl63t0uiSToxjbPgeeN_D kfkoTH0vS2gM5escHyLGe9rXXns6660.JmlqXCo1HTKl6.KCXp2G4vqW5FLAbWJnfvXB5rpvysNd P1CXiciDhgGyIu3szZLCI.ky_sfo_fAuq1IqP1zyScmhkmd.btkLyNZoyrB90C5aJWf49buu1aHx Y9W1o10o_qh8zdPNQ42veHNrRj523XQ7glrkcXu2yeKZfryBPRaCVQg3rxERj4G0kf.R7VqULDDE htYJ5oDGB9kxtkBTDtkOXceeuNC4KdBfG0M6ar9BYGTgmKwuDOWFN4IT5dKAMWBQMBUz331_i6Ml 0GUl1eg79t3qCgSMCuqByyNM_2es3mZN_1bQGQy4PFlCuxiOTVeGjJfMLPFsW7vVm0gYzOxy.1wy 840_AOK.luP6LqhOvzJHoZLUqtplsvNV_vgjqgu7DrFrBkqoASfEh3cVeVDPE2bo87_tcEEhV7ed aLq9KhbldWxH6TZ2fyqYu5Zw9MwdQewFy0FJMkz7zybwkm_CFkuPttVpC658JiNKY0siwW5VK7jr Att12NmAibdGDKgAsJYeXJSf_qPuuRohw0kBsvXNFI.BhPe5JiLmRTZwBzU2HNQX178T2EqDM8ch I5gqmTY8BJ0b0KAK84_geq8qIyMmeMNnnN3ljYNgjKkBDuxawdX54yy.xW5sSrCHg76vLdntyFys ewUWMjb0SvZNmCI95TUM97NEUTdWwG8nL2MnR0NIKUZ4Sle0Wo7fl3mD8Jf6gWakBkiMmL9yw Received: from sonic.gate.mail.ne1.yahoo.com by sonic301.consmr.mail.bf2.yahoo.com with HTTP; Tue, 15 Jan 2019 14:42:35 +0000 Date: Tue, 15 Jan 2019 14:42:31 +0000 (UTC) From: Pepe TD Vo Reply-To: Pepe TD Vo To: Thomas Kellerer , "pgsql-admin@lists.postgresql.org" Message-ID: <2088852869.450616.1547563351918@mail.yahoo.com> In-Reply-To: <298a21d9-c6b3-e80b-adf5-4583c9df2f70@gmx.net> References: <858026322.18309717.1547479488317.ref@mail.yahoo.com> <858026322.18309717.1547479488317@mail.yahoo.com> <298a21d9-c6b3-e80b-adf5-4583c9df2f70@gmx.net> Subject: Re: create tablespaces and users MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_450615_162942069.1547563351916" 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: 7570 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk ------=_Part_450615_162942069.1547563351916 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable so you suggest not to create the tablespace and associate with the database= , 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 ------=_Part_450615_162942069.1547563351916 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
so you suggest not to create the tablespace and asso= ciate with the database, right?  What's about the owner?  Still p= ostgres or create user owner?  From Oracle we have 4 schemas for cidr = database.

CREATE D= ATABASE "CIDR"
    WITH 
    OWNER = =3D postgres   --> or new users????
    ENCODING =3D 'UTF8'
    LC_COLLATE =3D '= en_US.UTF-8'
 =   LC_CTYPE =3D 'en_US.UTF-8'
    TABLESPACE =3D pg_default
    CONNECTION L= IMIT =3D -1;
 
t= hank 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 forgiv= e more.
To call him a dog hardly seems to do hi= m justice though in as much as he had four legs, a tail, and barked, I admi= t he was, to all outward appearances. But to those who knew him well, he wa= s a perfect gentleman (Hermione Gingold)

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


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:

> From oracle datab= ases, I have few tablespaces and users created for
> t= hat particular database.  How could I do the same for postgres?
<= br clear=3D"none">
The question is: what was the reason t= o use tablespaces in Oracle?

Most of = the time I see an Oracle installation with a tablespace per user, it's to m= anage space more easily.

As Postgres d= oes not store data in one huge file, this is not really relevant here.
As soon as a table is dropped, the space is released from th= e filesystem.

So just create the user= s and let them use the default tablespace, unless you used the tablespaces<= br clear=3D"none">to distribute the I/O load to different disks.

Thomas







------=_Part_450615_162942069.1547563351916--