Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eXWFT-00054c-1S for pgsql-docs@arkaria.postgresql.org; Fri, 05 Jan 2018 17:57:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eXWFS-0003uF-Hy for pgsql-docs@arkaria.postgresql.org; Fri, 05 Jan 2018 17:57:42 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eXWFS-0003u5-8o for pgsql-docs@lists.postgresql.org; Fri, 05 Jan 2018 17:57:42 +0000 Received: from mail.chartercom.com ([24.176.92.28]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eXWFP-0004LM-KT for pgsql-docs@postgresql.org; Fri, 05 Jan 2018 17:57:41 +0000 X-IronPort-AV: E=Sophos;i="5.46,319,1511848800"; d="scan'208";a="247095896" Received: from unknown (HELO SC58MEXGP034.CORP.CHARTERCOM.com) ([172.24.253.162]) by mail.chartercom.com with ESMTP; 05 Jan 2018 11:57:37 -0600 Received: from SC58MEXGP036.CORP.CHARTERCOM.com (172.24.253.164) by SC58MEXGP034.CORP.CHARTERCOM.com (172.24.253.162) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 5 Jan 2018 11:57:37 -0600 Received: from SC58MEXGP036.CORP.CHARTERCOM.com ([fe80::e82d:95f5:b81:9155]) by SC58MEXGP036.CORP.CHARTERCOM.com ([fe80::e82d:95f5:b81:9155%19]) with mapi id 15.00.1104.000; Fri, 5 Jan 2018 11:57:37 -0600 From: "Moser, Glen G" To: Stephen Frost CC: "pgsql-docs@postgresql.org" Subject: RE: Is this still accurate? Thread-Topic: Is this still accurate? Thread-Index: AdOGRieX8PI45mfVS1CZ/fqv3WTc7wAAmIZgAACc4cAADWOZAAAMiN1A Date: Fri, 5 Jan 2018 17:57:37 +0000 Message-ID: <68e5e2554e2240c6a22bd384fa7c9659@SC58MEXGP036.CORP.CHARTERCOM.com> References: <4fe11dc1b660433594624b280b8ad832@SC58MEXGP036.CORP.CHARTERCOM.com> <3d7cd4673a80438798ad20b83411e3ca@SC58MEXGP001.CORP.CHARTERCOM.com> <1646547df04f4555a548ad7815208d5f@SC58MEXGP036.CORP.CHARTERCOM.com> <20180105175438.GO2416@tamriel.snowman.net> In-Reply-To: <20180105175438.GO2416@tamriel.snowman.net> 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: [172.24.253.192] Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk That's really the gist of the concern from a team member of mine. Not that= the 4TB number is wrong but that it could be misleading to assume that 4TB= is some sort of upper bound. That's how this concern was relayed to me and I am just following up. Glen Moser Director, Reporting & Analytics, NOC Charter Communications 636.387.6888 (O) | 314.308.5680 (M) -----Original Message----- From: Stephen Frost [mailto:sfrost@snowman.net] = Sent: Friday, January 05, 2018 11:55 AM To: Moser, Glen G Cc: pgsql-docs@postgresql.org Subject: Re: Is this still accurate? Greetings, * Moser, Glen G (Glen.Moser@charter.com) wrote: > Can someone confirm the accuracy of the information found at https://www.= postgresql.org/about/? > = > Specifically the maximum data values in the screen shot below...it seems = as though this documentation might be out of date. The part you highlighted was: "There are active PostgreSQL systems in production environments that manage= in excess of 4 terabytes of data." Which is pretty accurate, I know of some myself that are larger than 4TB. = That 4TB number isn't a limit of any kind and the sentence says "in excess = of" meaning that there are databases larger than that. There's actually some which are quite a bit larger than that, in fact. We could bump the number up there or remove the sentence, but I don't think= there's anything inaccurate about the statement. Thanks! Stephen E-MAIL CONFIDENTIALITY NOTICE: = The contents of this e-mail message and any attachments are intended solely= for the addressee(s) and may contain confidential and/or legally privilege= d information. If you are not the intended recipient of this message or if = this message has been addressed to you in error, please immediately alert t= he sender by reply e-mail and then delete this message and any attachments.= If you are not the intended recipient, you are notified that any use, diss= emination, distribution, copying, or storage of this message or any attachm= ent is strictly prohibited.