From: Yves Dorfsman <yves@zioup.com>
To: pgsql-performance@postgresql.org
Subject: Re: unlogged tables
Date: Mon, 13 Apr 2015 14:30:49 -0600
Message-ID: <552C2779.8050004@zioup.com> (raw)
In-Reply-To: <1428956174244-5845580.post@n5.nabble.com>
References: <005501cca0ad$b9478440$2bd68cc0$@devshock.com>
<1428953502160-5845576.post@n5.nabble.com>
<CAJghg4+NoOaip1VaBK9+cY-LYjmUr_9kFNZ3sdWq5wQRNVc9HA@mail.gmail.com>
<1428956174244-5845580.post@n5.nabble.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
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
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: yves@zioup.com
Subject: Re: unlogged tables
In-Reply-To: <552C2779.8050004@zioup.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