pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Anibal David Acosta <aa@devshock.com>
To: pgsql-performance@postgresql.org
Subject: unlogged tables
Date: Fri, 11 Nov 2011 17:08:44 -0300
Message-ID: <005501cca0ad$b9478440$2bd68cc0$@devshock.com> (raw)

Hello, just for clarification.

 

Unlogged tables are not memory tables don't?

 

If we stop postgres server (normal stop) and start again, all information in
unlogged tables still remain?

 

So, can I expect a data loss just in case of crash, power failure or SO
crash don't?

 

In case of crash, is possible that data corruption happened in a unlogged
tables?

 

For performance purpose can I use async commit and unlogged tables?

 

 

Thanks!

 

 

 

 

view thread (42+ messages)  latest in thread

Message-ID: <005501cca0ad$b9478440$2bd68cc0$@devshock.com>
Permalink:  ../005501cca0ad$b9478440$2bd68cc0$@devshock.com/
Also on:    postgresql.org/message-id/005501cca0ad$b9478440$2bd68cc0$@devshock.com

copy link · copy postgr.es

reply

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: aa@devshock.com
  Subject: Re: unlogged tables
  In-Reply-To: <005501cca0ad$b9478440$2bd68cc0$@devshock.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