Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Yi2yD-0004pT-Gg for pgsql-performance@arkaria.postgresql.org; Tue, 14 Apr 2015 15:41:49 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Yi2yC-0001tk-VK for pgsql-performance@arkaria.postgresql.org; Tue, 14 Apr 2015 15:41:49 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1Yi2yB-0001qh-60 for pgsql-performance@postgresql.org; Tue, 14 Apr 2015 15:41:47 +0000 Received: from smtp-out-01.shaw.ca ([64.59.136.137]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Yi2y6-0001ez-6Q for pgsql-performance@postgresql.org; Tue, 14 Apr 2015 15:41:45 +0000 X-Cloudmark-SP-Filtered: true X-Cloudmark-SP-Result: v=1.1 cv=BkBxTXsSVzyY7C2joSQK+JNK4mJr1It1Skr7Xe8+Jh8= c=1 sm=1 a=motdEeDeaRIA:10 a=BLceEmwcHowA:10 a=IkcTkHD0fZMA:10 a=1AzCEyHvRsrOnBOCSdCQag==:17 a=N8iSzGwtAAAA:8 a=Xzj5fuOlYcKBNXdjLMEA:9 a=QEXdDO2ut3YA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117 Received: from unknown (HELO home.zioup.com) ([70.72.160.156]) by smtp-out-01.shaw.ca with ESMTP; 14 Apr 2015 09:41:38 -0600 Received: from [192.168.2.80] (epicurus.zioup.net [192.168.2.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by home.zioup.com (Postfix) with ESMTPSA id A248BA035F for ; Tue, 14 Apr 2015 09:41:38 -0600 (MDT) Message-ID: <552D3532.5020807@zioup.com> Date: Tue, 14 Apr 2015 09:41:38 -0600 From: Yves Dorfsman User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Re: unlogged tables References: <005501cca0ad$b9478440$2bd68cc0$@devshock.com> <1428953502160-5845576.post@n5.nabble.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) 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 On 2015-04-13 17:49, Jeff Janes wrote: > > One way would be to lock dirty buffers from unlogged relations into > shared_buffers (which hardly seems like a good thing) until the start of a > "super-checkpoint" and then write them all out as fast as possible (which kind > of defeats checkpoint_completion_target). And then if the crash happened > during a super-checkpoint, the data would still be inconsistent and need to be > truncated. > What do you call a "super-checkpoint"? -- http://yves.zioup.com gpg: 4096R/32B0F416 -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance