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 1gXTyZ-0005XJ-28 for pgsql-novice@arkaria.postgresql.org; Thu, 13 Dec 2018 16:36:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gXTyX-0007Dg-Oy for pgsql-novice@arkaria.postgresql.org; Thu, 13 Dec 2018 16:36:37 +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 1gXTyX-0007DV-IW; Thu, 13 Dec 2018 16:36:37 +0000 Received: from 062066187220.dynamic.telenor.dk ([62.66.187.220] helo=shrek.krogh.cc) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gXTyV-0003Mz-Li; Thu, 13 Dec 2018 16:36:37 +0000 Received: from localhost (localhost [127.0.0.1]) by shrek.krogh.cc (Postfix) with ESMTP id 7EB381F0071A; Thu, 13 Dec 2018 17:36:22 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at shrek.krogh.cc Received: from shrek.krogh.cc ([127.0.0.1]) by localhost (shrek.krogh.cc [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CalO98AVF_vi; Thu, 13 Dec 2018 17:36:19 +0100 (CET) Received: from [2.131.117.202] (unknown [2.131.117.202]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jesper@krogh.cc) by shrek.krogh.cc (Postfix) with ESMTPSA id 9A2921F006C7; Thu, 13 Dec 2018 17:36:19 +0100 (CET) Content-Type: multipart/alternative; boundary=Apple-Mail-BB39B0EA-2C60-4DDF-A159-CDDE6A010F50 Mime-Version: 1.0 (1.0) Subject: Re: Postgres size greater than 1TB From: Jesper Krogh X-Mailer: iPhone Mail (16B92) In-Reply-To: <7a8352b4dbbb46878fe6e26ab96cec3d@DC03PXMBP003.jacksonnational.com> Date: Thu, 13 Dec 2018 17:36:28 +0100 Cc: "pgsql-sql@lists.postgresql.org" , "pgsql-novice@lists.postgresql.org" Content-Transfer-Encoding: 7bit Message-Id: <7B765BEB-87D2-4921-8ABC-683ABE939EE2@krogh.cc> References: <7a8352b4dbbb46878fe6e26ab96cec3d@DC03PXMBP003.jacksonnational.com> To: "Rossi, Maria" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --Apple-Mail-BB39B0EA-2C60-4DDF-A159-CDDE6A010F50 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable > On 13 Dec 2018, at 17.33, Rossi, Maria wrote: >=20 > Hi, > =20 > In the past, our postgres cluster data_directory is a file system that is <= 1TB > =20 > Our postgresconf.cfg has this: > =20 > data_directory =3D '/dba/psg/gp08/pg_data' > =20 > 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? we have filesystems above 100TB. where do you see this limit? Jesper=20= --Apple-Mail-BB39B0EA-2C60-4DDF-A159-CDDE6A010F50 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit

On 13 Dec 2018, at 17.33, Rossi, Maria <maria.rossi@jackson.com> wrote:

Hi,

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

Our postgresconf.cfg has this:

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

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

Any suggestion on how to handle this?

we have filesystems above 100TB. where do you see this limit?

Jesper

--Apple-Mail-BB39B0EA-2C60-4DDF-A159-CDDE6A010F50--