From: Stephen Frost <sfrost@snowman.net>
To: Anibal David Acosta <aa@devshock.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: unlogged tables
Date: Fri, 11 Nov 2011 15:18:22 -0500
Message-ID: <20111111201822.GN24234@tamriel.snowman.net> (raw)
In-Reply-To: <005501cca0ad$b9478440$2bd68cc0$@devshock.com>
References: <005501cca0ad$b9478440$2bd68cc0$@devshock.com>
* Anibal David Acosta (aa@devshock.com) wrote:
> Unlogged tables are not memory tables don't?
Unlogged tables are not memory tables.
> If we stop postgres server (normal stop) and start again, all information in
> unlogged tables still remain?
Yes.
> So, can I expect a data loss just in case of crash, power failure or SO
> crash don't?
Yes.
> In case of crash, is possible that data corruption happened in a unlogged
> tables?
In a crash, unlogged tables are automatically truncated.
> For performance purpose can I use async commit and unlogged tables?
I'm not aware of any issues (beyond those already documented for async
commit..) with having async commit and unlogged tables.
THanks,
Stephen
Attachments:
signature.asc (application/pgp-signature, 197B) download
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: sfrost@snowman.net, aa@devshock.com
Subject: Re: unlogged tables
In-Reply-To: <20111111201822.GN24234@tamriel.snowman.net>
* 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