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@xxxxxxxxxxxx] Enviado el: lunes, 14 de noviembre de 2011 02:27 p.m. Para: 'Richard Huxton'; Anibal David Acosta; 'Sergey Konoplev' CC: pgsql-performance@xxxxxxxxxxxxxx; 'Stephen Frost' Asunto: Re: unlogged tables "Anibal David Acosta" <aa@xxxxxxxxxxxx> 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 -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
