From: Thomas Kellerer <spam_eater@gmx.net>
To: pgsql-admin@postgresql.org
Subject: Re: PITR compatible backup with exclusion
Date: Sat, 14 Mar 2015 12:59:12 +0100
Message-ID: <me17qj$q4h$1@ger.gmane.org> (raw)
In-Reply-To: <1426332627.3775.4.camel@gmail.com>
References: <CA+Cf-b8BBFPq5HLa5TZwHgpn0gpWNDGTwE24ydvOn3QhdrLRPg@mail.gmail.com>
<ma7f5t$dnj$1@ger.gmane.org>
<1426332627.3775.4.camel@gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: spam_eater@gmx.net
Subject: Re: PITR compatible backup with exclusion
In-Reply-To: <me17qj$q4h$1@ger.gmane.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox