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 1gXTvL-0005K2-0X for pgsql-sql@arkaria.postgresql.org; Thu, 13 Dec 2018 16:33:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gXTvI-0001lS-4B for pgsql-sql@arkaria.postgresql.org; Thu, 13 Dec 2018 16:33:16 +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 1gXTvH-0001lH-Ou; Thu, 13 Dec 2018 16:33:15 +0000 Received: from dc01pesav001.jacksonnational.com ([12.34.36.90]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gXTvC-0003Gt-Iv; Thu, 13 Dec 2018 16:33:14 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=jackson.com; i=@jackson.com; q=dns/txt; s=Internal; t=1544718791; x=1576254791; h=from:to:subject:date:message-id:mime-version; bh=GVXv1ie2N/GYYyY+SwhAdBwctqCz9KEzIaXmIKXO1dg=; b=TR4LnGoTtE7HVGvHND/NJgYhGi+3UMHyylZWRWakSKsAvW8uwbpuxEmz QO/IlIqJ+F/yqM2ksWUvVZ+gmQPYWugVRbZ2fgVBtkPV1L5e5pgzGdrZD 52OJNOYwRb5834vDJvrttCGDgHBdD2yn32gWdFl3kd2FX1usg0jmrlsBU I=; X-IronPort-AV: E=Sophos;i="5.56,349,1539662400"; d="scan'208,217";a="30282590" Received: from dc0xpdlpv002.jacksonnational.com (HELO DC03PXMBP003.jacksonnational.com) ([10.5.49.47]) by DC01PESAV001.jacksonnational.com with ESMTP; 13 Dec 2018 11:33:04 -0500 Received: from DC03PXMBP003.jacksonnational.com (10.12.105.32) by DC03PXMBP003.jacksonnational.com (10.12.105.32) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Thu, 13 Dec 2018 11:33:03 -0500 Received: from DC03PXMBP003.jacksonnational.com ([10.12.105.32]) by DC03PXMBP003.jacksonnational.com ([10.12.105.32]) with mapi id 15.00.1367.000; Thu, 13 Dec 2018 11:33:03 -0500 From: "Rossi, Maria" To: "'pgsql-sql@lists.postgresql.org'" , "'pgsql-novice@lists.postgresql.org'" Subject: Postgres size greater than 1TB Thread-Topic: Postgres size greater than 1TB Thread-Index: AdSTAW88lpCAOld3TI2D7spWyhsgag== Date: Thu, 13 Dec 2018 16:33:03 +0000 Message-ID: <7a8352b4dbbb46878fe6e26ab96cec3d@DC03PXMBP003.jacksonnational.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.12.16.10] x-tm-as-product-ver: SMEX-12.5.0.1300-8.5.1010-24282.006 x-tm-as-result: No-17.019400-5.000000-10 x-tmase-matchedrid: EQOIcCJ9jA1HW+94FA8JF8K1Ib9JAALxrogFtKd/P7eW+zaNLK605Oyg QWdkAVMs0Nt5/j+aSDEUI4s17Ql301mKiy1F9pgLQesjq8XPMbt3Bf9JIqsoeEbaqUVvLFsiakc q2RAHKcpj6nYvURA3nSTDX0HcFwsWgiIO7Sf/7rGL6bUMM+bbIv98fIf4wIXluu0N7j6PSiPSnf YnnxZmsm6hhEFlyQug+0gY6okUAw+mSRekxKkbnJJSy10yJkGuZUlQUP70sAhF6yga/Gq9suCfw dXr9Uztu7C4hieFwVJ/JgN7Aw6tANxWF9NJ0ly4H2TDzR13hu7xneSaHRJg74dZyLZ/EsYlfQGd PK1MIbl/dOftgUTSzCEfunzqfi01 x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No x-tmase-result: 10--17.019400-5.000000 x-tmase-version: SMEX-12.5.0.1300-8.5.1010-24282.006 Content-Type: multipart/alternative; boundary="_000_7a8352b4dbbb46878fe6e26ab96cec3dDC03PXMBP003jacksonnati_" MIME-Version: 1.0 X-CFilter-Loop: Reflected List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --_000_7a8352b4dbbb46878fe6e26ab96cec3dDC03PXMBP003jacksonnati_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, In the past, our postgres cluster data_directory is a file system that is <= 1TB Our postgresconf.cfg has this: data_directory =3D '/dba/psg/gp08/pg_data' Now, we need a new cluster that needs more than 1TB (Unix has a limit of 1= TB for file systems) Any suggestion on how to handle this? Can I specify more than 1 path in my data_directory? Can I create a tablespace in a new file system/directory? Any help would be appreciated. Thanks Maria --_000_7a8352b4dbbb46878fe6e26ab96cec3dDC03PXMBP003jacksonnati_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

In the past, our postgres cluster data_directory is = a file system that is < 1TB

 

Our postgresconf.cfg has this:

 

data_directory =3D '/dba/= psg/gp08/pg_data'

 

Now,  we need a new cluster that needs more tha= n 1TB (Unix has a limit of 1TB for file systems)

Any suggestion on how to handle this?

Can I specify more than 1 path in  my data_dire= ctory?

Can I create a tablespace in a new file system/direc= tory?

 

Any help would  be appreciated.

Thanks

 

Maria

 

--_000_7a8352b4dbbb46878fe6e26ab96cec3dDC03PXMBP003jacksonnati_--