Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 604672049F7 for ; Fri, 11 Nov 2011 16:14:46 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 61414-06 for ; Fri, 11 Nov 2011 20:14:40 +0000 (UTC) X-Greylist: delayed 00:05:50.610122 by SQLgrey-1.8.0-rc2 Received: from mail-gx0-f174.google.com (mail-gx0-f174.google.com [209.85.161.174]) by mail.postgresql.org (Postfix) with ESMTP id E92F52049F6 for ; Fri, 11 Nov 2011 16:14:39 -0400 (AST) Received: by ggnb2 with SMTP id b2so4548841ggn.19 for ; Fri, 11 Nov 2011 12:14:39 -0800 (PST) Received: by 10.101.57.14 with SMTP id j14mr5965805ank.112.1321042128418; Fri, 11 Nov 2011 12:08:48 -0800 (PST) Received: from AnibalVAIO ([200.85.32.68]) by mx.google.com with ESMTPS id i31sm14566654anm.19.2011.11.11.12.08.45 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 11 Nov 2011 12:08:47 -0800 (PST) From: "Anibal David Acosta" To: Subject: unlogged tables Date: Fri, 11 Nov 2011 17:08:44 -0300 Message-ID: <005501cca0ad$b9478440$2bd68cc0$@devshock.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0056_01CCA094.93FB84C0" X-Mailer: Microsoft Outlook 14.0 Thread-Index: AcygrLZ+T6hIE67kQG6bpqeeD6QnmQ== Content-Language: es-py X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.899 tagged_above=-10 required=5 tests=BAYES_00=-1.9, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 201111/145 X-Sequence-Number: 45656 This is a multipart message in MIME format. ------=_NextPart_000_0056_01CCA094.93FB84C0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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! ------=_NextPart_000_0056_01CCA094.93FB84C0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

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!

------=_NextPart_000_0056_01CCA094.93FB84C0--