Received: from maia.hub.org (maia-2.hub.org [200.46.204.251])
	by mail.postgresql.org (Postfix) with ESMTP id C461B1435024
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Fri, 11 Nov 2011 16:18:28 -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 63167-07
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Fri, 11 Nov 2011 20:18:22 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0-rc2
Received: from tamriel.snowman.net (tamriel.snowman.net [72.66.115.51])
	by mail.postgresql.org (Postfix) with ESMTP id C35331435023
	for <pgsql-performance@postgresql.org>;
	Fri, 11 Nov 2011 16:18:22 -0400 (AST)
Received: by tamriel.snowman.net (Postfix, from userid 1000)
	id 50F42229ED; Fri, 11 Nov 2011 15:18:22 -0500 (EST)
Date: Fri, 11 Nov 2011 15:18:22 -0500
From: Stephen Frost <sfrost@snowman.net>
To: Anibal David Acosta <aa@devshock.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: unlogged tables
Message-ID: <20111111201822.GN24234@tamriel.snowman.net>
References: <005501cca0ad$b9478440$2bd68cc0$@devshock.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="VQl1xLnQPIyet9qq"
Content-Disposition: inline
In-Reply-To: <005501cca0ad$b9478440$2bd68cc0$@devshock.com>
X-Editor: Vim http://www.vim.org/
X-Info: http://www.snowman.net
X-Operating-System: Linux/2.6.32-5-amd64 (x86_64)
X-Uptime: 15:17:07 up 282 days,  4:47, 24 users,  load average: 0.00, 0.02,
	0.00
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-3.101 tagged_above=-10 required=5
	tests=BAYES_00=-1.9, RP_MATCHES_RCVD=-1.201
X-Spam-Level: 
X-Archive-Number: 201111/146
X-Sequence-Number: 45657


--VQl1xLnQPIyet9qq
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

* 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

--VQl1xLnQPIyet9qq
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk69gw4ACgkQrzgMPqB3kiiZeQCfbGjZ2HqS0975jQT1WmZuhBhm
s6MAn0iykDJM3qcGGs1AU1OCCTzsSdgt
=I8wV
-----END PGP SIGNATURE-----

--VQl1xLnQPIyet9qq--