To: pgsql-admin@postgresql.org
From: Thomas Kellerer <spam_eater@gmx.net>
Subject: Re: PITR compatible backup with exclusion
Date: Sat, 14 Mar 2015 12:59:12 +0100
Lines: 17
Message-ID: <me17qj$q4h$1@ger.gmane.org>
References: 
 <CA+Cf-b8BBFPq5HLa5TZwHgpn0gpWNDGTwE24ydvOn3QhdrLRPg@mail.gmail.com>	
 <ma7f5t$dnj$1@ger.gmane.org> <1426332627.3775.4.camel@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de;
 rv:1.8.1.21) Gecko/20090302 Thunderbird/2.0.0.21 Mnenhy/0.7.5.666
In-Reply-To: <1426332627.3775.4.camel@gmail.com>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

jaime soler wrote on 14.03.2015 12:30:
>> What if you change that big table to UNLOGGED?
>> As unlogged tables don't generate WAL they don't contribute to the PITR "restore time"
>> (and they won't be restored if you have to do a PITR!)
>
> However, they are not crash-safe: an unlogged table is automatically
> truncated after a crash or unclean shutdown.

That is correct, but Martin wrote in the initial question:

> The backup of the table itself is also reduntant,
>as the table data can be recreated by importing from the source files

So if the data lost, it apparently doesn't matter.


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin