From: | Andreas Kretschmer <akretschmer(at)spamfence(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: asynchronous commit |
Date: | 2015-01-20 17:21:35 |
Message-ID: | 20150120172135.GB16478@tux |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Robert DiFalco <robert(dot)difalco(at)gmail(dot)com> 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°
From | Date | Subject | |
---|---|---|---|
Next Message | deans | 2015-01-21 01:54:13 | Re: BDR Error restarted |
Previous Message | agent | 2015-01-20 11:53:28 | Re: BDR Error restarted |