Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Yhl0T-0007uc-M3 for pgsql-performance@arkaria.postgresql.org; Mon, 13 Apr 2015 20:30:57 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Yhl0T-0001uS-2H for pgsql-performance@arkaria.postgresql.org; Mon, 13 Apr 2015 20:30:57 +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 1Yhl0S-0001uK-62 for pgsql-performance@postgresql.org; Mon, 13 Apr 2015 20:30:56 +0000 Received: from smtp-out-03.shaw.ca ([64.59.136.139]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Yhl0O-0007jf-4V for pgsql-performance@postgresql.org; Mon, 13 Apr 2015 20:30:53 +0000 X-Cloudmark-SP-Filtered: true X-Cloudmark-SP-Result: v=1.1 cv=tLeJwtg1FCvAouMblIYY1Z5/U6XdMrtw4y2B9g+QINc= c=1 sm=1 a=motdEeDeaRIA:10 a=BLceEmwcHowA:10 a=IkcTkHD0fZMA:10 a=1AzCEyHvRsrOnBOCSdCQag==:17 a=N8iSzGwtAAAA:8 a=Gb-LMZaLwfUWzAt1fecA:9 a=QEXdDO2ut3YA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117 Received: from unknown (HELO home.zioup.com) ([70.72.160.156]) by smtp-out-03.shaw.ca with ESMTP; 13 Apr 2015 14:30:50 -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 E7CE5A03B0 for ; Mon, 13 Apr 2015 14:30:49 -0600 (MDT) Message-ID: <552C2779.8050004@zioup.com> Date: Mon, 13 Apr 2015 14:30:49 -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> <1428956174244-5845580.post@n5.nabble.com> In-Reply-To: <1428956174244-5845580.post@n5.nabble.com> 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 14:16, dgabriel wrote: > That will be a very useful feature. I agree, unlogged tables would be a lot more useful if they didn't "disappear" on re-start. > could be expensive. Also i have to detect when postgres crush, i have no > idea how i can detect if postgres crushed. Then i have somehow to attache a > script at postgres start, to restore the dumps...the dump solution is very > complicate and unreliable. A periodic flush feature will be amazing! In my experience postgres is very aggressive in getting rid of unlogged tables, it does get rid of them from shutdowns that seem perfectly fine (no crash). A lot of people get surprised by this. -- 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