From: "Anibal David Acosta" <aa@devshock.com>
To: "'Kevin Grittner'" <Kevin.Grittner@wicourts.gov>,
	"'Richard Huxton'" <dev@archonet.com>,
	"'Sergey Konoplev'" <gray.ru@gmail.com>
Cc: <pgsql-performance@postgresql.org>, "'Stephen Frost'" <sfrost@snowman.net>
References: <005501cca0ad$b9478440$2bd68cc0$@devshock.com>
	<20111111201822.GN24234@tamriel.snowman.net>
	<CAL_0b1t02q77ft2JWdjMv8q4vaGm=x__K0rzVkpNSvSy2-SjzA@mail.gmail.com>
	<4EC0D827.8090601@archonet.com>
	<CAL_0b1tuxi9YVhGKsNUSTZCUBXgOmppan7w+KkRZARbQ=u4P5w@mail.gmail.com>
	<4EC0EAD6.9010302@archonet.com>
	<CAL_0b1sSyTgMUxcRi+2ibTHHV4-qH3fvacsQUCbbeBsu0jYGAQ@mail.gmail.com>
	<00ea01cca2ef$abcf3a30$036dae90$@devshock.com>
	<4EC0FAE80200002500042E6C@gw.wicourts.gov>
In-Reply-To: <4EC0FAE80200002500042E6C@gw.wicourts.gov>
Subject: Re: unlogged tables
Date: Mon, 14 Nov 2011 14:38:31 -0300
Message-ID: <00ff01cca2f4$3cb86860$b6293920$@devshock.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: 
 AQG0h8c2HxwgVHVwA7Oudni7xLo/1gKNzE9QAZGzEw4Bc7WZpAHcxNALAamzBiMCHqGblQJY0lSEApP7xZ+VW61cgA==
Content-Language: es-py

I am doing asynchronous commit but sometimes I think that there are so  many
"things" in an insert/update transaction, for a table that has not too much
important information.

My table is a statistics counters table, so I can live with a partial data
loss, but not with a full data loss because many counters are weekly and
monthly.

Unlogged table can increase speed, this table has about 1.6 millions of
update per hour, but unlogged with a chance of loss all information on a
crash are not a good idea for this.

Anyway, thanks Kevin!


-----Mensaje original-----
De: Kevin Grittner [mailto:Kevin.Grittner@wicourts.gov] 
Enviado el: lunes, 14 de noviembre de 2011 02:27 p.m.
Para: 'Richard Huxton'; Anibal David Acosta; 'Sergey Konoplev'
CC: pgsql-performance@postgresql.org; 'Stephen Frost'
Asunto: Re: [PERFORM] unlogged tables

"Anibal David Acosta" <aa@devshock.com> wrote:
 
> Maybe an option like "Recover from file " will be useful So, for 
> example, daily some process do a COPY of entire table to a file
> 
> In case of crash postgres recover content from the file.
 
If you need to recover file contents on a crash, then an unlogged table is
probably not the right choice.  There is always asynchronous commit.
 
-Kevin