Search Postgresql Archives

Re: asynchronous commit

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Robert DiFalco <robert.difalco@xxxxxxxxx> wrote:

> Andreas, I think UNLOGGED would be something different but I'm not totally
> clear. However, it seems to me that an unlogged table would simply disappear
> (be truncated) after a server crash. That means instead of maybe loosing a
> record or two that I could loose a ton or records. But maybe my understanding
> is off.

That's correct.


Maybe you can solve the performance issue with unlogged tables, but yes,
you have to save the records into a regular table. Maybe via Cron or so.
(rough, with move as (delete from unlogged returning *) insert into
regular_table select * from move, or something similar.) 


Sorry for the delay.


Andreas
-- 
Really, I'm not out to destroy Microsoft. That will just be a completely
unintentional side effect.                              (Linus Torvalds)
"If I was god, I would recompile penguin with --enable-fly."   (unknown)
Kaufbach, Saxony, Germany, Europe.              N 51.05082°, E 13.56889°


-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux