"Anibal David Acosta" <aa@devshock.com> wrote:
> 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.
pg_dump -t 'tablename' from a cron job? (Make sure to rotate dump
file names, maybe with day of week or some such.)
-Kevin
