Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XMcp9-0000o3-1O for pgsql-performance@arkaria.postgresql.org; Wed, 27 Aug 2014 12:59:39 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XMcp7-0006Hl-PN for pgsql-performance@arkaria.postgresql.org; Wed, 27 Aug 2014 12:59:37 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XMcp5-0006D0-8O for pgsql-performance@postgresql.org; Wed, 27 Aug 2014 12:59:35 +0000 Received: from nm8-vm5.bullet.mail.ne1.yahoo.com ([98.138.91.230]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XMcp1-0008Dk-2A for pgsql-performance@postgresql.org; Wed, 27 Aug 2014 12:59:33 +0000 Received: from [98.138.100.102] by nm8.bullet.mail.ne1.yahoo.com with NNFMP; 27 Aug 2014 12:59:29 -0000 Received: from [98.138.226.169] by tm101.bullet.mail.ne1.yahoo.com with NNFMP; 27 Aug 2014 12:59:29 -0000 Received: from [127.0.0.1] by omp1070.mail.ne1.yahoo.com with NNFMP; 27 Aug 2014 12:59:29 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 515387.60425.bm@omp1070.mail.ne1.yahoo.com Received: (qmail 2602 invoked by uid 60001); 27 Aug 2014 12:59:29 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ymail.com; s=s1024; t=1409144369; bh=5aWkdtgO+5UJA7uVYPhNrW4fAzw2K8B5aLtWp59TtIc=; h=References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=g28T5joOqFbBGH6Eicyw/XSBDOcWD1QB/QX9lbuDmITB75N/m/aqz5DTe4RZBC86EsdybGHNmGcEYhAR4CNDe+DZebJkRe/iQsUrO6wLTUh0bQB3xRp1t/nPwDsvjtPmbVDGb36IhBbXo3eLe0UvebEfhfESJV6p6QEoh+vZk5E= X-YMail-OSG: JPZhzKgVM1k8tj7bPL8tJ1nlZRaPiGBn3YQLyhCRGMbfuJp Ll3sCHFqzlZF6VSCtMYmA.ffYzHH9tXMi_p3j04C51x2OOWUYbotG8U6si20 31RxcA0bMBmHa0G5gq0YTK5nc0rJn2OSRZx2G7VZJNysHHGPwifr_e6VWcsB hyi3pc2teZ6mwiFQFqQ4HfO_448OCPsGoTsrT0x30Hb7QHPGMCOzQpq_B3RC eTpfxmqrrEKMqRu8Ejzj87BEXPZUReRZN0mZYazOp.9_OnyF0s0L0Dj1xP64 aEZIM7ydBQwW6EPhg1DdMkLhccqv5TjyEnPc5SPOS14MEcb7NHIo875BMsVF awblZn4JQSsOsdJDlad61tUn_TmXlIb1Do0.Lc4lEDOwfR2LUVuMM9VBWVoA DbtfX6KAAjmgcUF4zkoCKxrADIU2umvigZMGnKuaCk.FoLxdnVc5Hr.8mJq7 Cd2TmOqyC3GMyAnw3HsciICLX186MEIep3tUI04k_DHW_7eUEPy3vTzcKbhS uQOZYoqivcGZWsIidvvl9cc5XAJMLxGx2FmqMMof014fTFZ9.Kh05dZUA0Zu i22ZgctipCZ_TTHiyosHyAPawfaj5r9he.bltla_U Received: from [24.178.25.147] by web122306.mail.ne1.yahoo.com via HTTP; Wed, 27 Aug 2014 05:59:29 PDT X-Rocket-MIMEInfo: 002.001, QWxleCBHb25jaGFyb3YgPGFsZXguZ29uY2hhcm92LnVzYUBnbWFpbC5jb20.IHdyb3RlOgo.IEtldmluIEdyaXR0bmVyIDxrZ3JpdHRuQHltYWlsLmNvbT4gd3JvdGU6Cgo.PiBUaGUgcm93cyB3aWxsIGFsbCBiZSBpbiB0aGUgdGFibGUsIGJ1dCBub3QgdmlzaWJsZSB0byBhbnkgb3RoZXIKPj4gdHJhbnNhY3Rpb24uCj4KPiBIb3cgbXVjaCBkYXRhIGNhbiBJIGZpdCB0aGVyZSB3aGlsZSBkb2luZyBDT1BZP8KgIE5vdCAxIFRCPwoKQXMgaGFzIGFscmVhZHkgYmVlbiBzYWlkLCB3aHkgbm90P8KgIFRoaXMgaXMBMAEBAQE- X-Mailer: YahooMailWebService/0.8.201.700 References: <53F7ACF4.1010604@encs.concordia.ca> <1409092428.41025.YahooMailNeo@web122306.mail.ne1.yahoo.com> Message-ID: <1409144369.45962.YahooMailNeo@web122306.mail.ne1.yahoo.com> Date: Wed, 27 Aug 2014 05:59:29 -0700 From: Kevin Grittner Reply-To: Kevin Grittner Subject: Re: autocommit (true/false) for more than 1 million records To: Alex Goncharov Cc: "pgsql-performance@postgresql.org" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org Alex Goncharov wrote: > Kevin Grittner wrote: >> The rows will all be in the table, but not visible to any other >> transaction. > > How much data can I fit there while doing COPY?=A0 Not 1 TB? As has already been said, why not?=A0 This is not some special section of the table -- the data is written to the table.=A0 Period. Commit or rollback just tells new transactions whether data flagged with that transaction number is visible. Nobody can tell you how much space that will take -- it depends on many factors, including how many columns of what kind of data, how compressible it is, and how it is indexed.=A0 But the point is, we are not talking about any separate space from what is needed to store the data in the database. FWIW, I think the largest single COPY statement I ever ran was generated by pg_dump and piped directly to psql for a major release upgrade (before pg_upgrade was available), and it was somewhere in the 2TB to 3TB range.=A0 It took a long time, but it "just worked". That should be true for 10TB or 100TB, as long as you have sized the machine correctly and are loading clean data.=A0 Whether you have that covered, and how you want to "hedge your bets" based on your degree of confidence in those things is a judgment call.=A0 When I'm=20 in the position of needing to make such a call, I like to do some=20 tests. -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company --=20 Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance