From: dgabriel <gabriel.dodan@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: unlogged tables
Date: Tue, 14 Apr 2015 08:56:10 -0700 (MST)
Message-ID: <1429026970751-5845650.post@n5.nabble.com> (raw)
In-Reply-To: <CAKFQuwYtdCF1BFx7pji78tshjUD-oVCoOOnBcr935_tq5gY-Ag@mail.gmail.com>
References: <005501cca0ad$b9478440$2bd68cc0$@devshock.com>
<1428953502160-5845576.post@n5.nabble.com>
<CAJghg4+NoOaip1VaBK9+cY-LYjmUr_9kFNZ3sdWq5wQRNVc9HA@mail.gmail.com>
<CAKFQuwYtdCF1BFx7pji78tshjUD-oVCoOOnBcr935_tq5gY-Ag@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
David G Johnston wrote
> Well, that is half right anyway. UNLOGGED tables obey checkpoints just
> like any other table. The missing feature is an option to leaved restored
> the last checkpoint. Instead, not knowing whether there were changes
> since the last checkpoint, the system truncated the relation.
>
> What use case is there for a behavior that the last checkpoint data is
> left on the relation upon restarting - not knowing whether it was possible
> the other data could have been written subsequent?
If is possible to restore the table at last checkpoint state that will be
more than enough. I don't care about the changes since last checkpoint, I am
willing to lose those changes. There are use cases where is acceptable to
lose some data, for example in a cache system, it is not a big issue if we
lose some cached data.
--
View this message in context: http://postgresql.nabble.com/unlogged-tables-tp4985453p5845650.html
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
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-performance@postgresql.org
Cc: gabriel.dodan@gmail.com
Subject: Re: unlogged tables
In-Reply-To: <1429026970751-5845650.post@n5.nabble.com>
* 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