Robert DiFalco 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 o
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
understa
Robert DiFalco wrote:
> I have several tables that I use for logging and real-time stats. These are
> not
> critical and since they are a bottleneck I want transactions against them to
> always be asynchronous. Is there a way to specify this at a table level or do
> I
> have to make sure to cal
On Mon, Jan 19, 2015 at 10:03 AM, Robert DiFalco
wrote:
> I have several tables that I use for logging and real-time stats. These
> are not critical and since they are a bottleneck I want transactions
> against them to always be asynchronous. Is there a way to specify this at a
> table level or d
I have several tables that I use for logging and real-time stats. These are
not critical and since they are a bottleneck I want transactions against
them to always be asynchronous. Is there a way to specify this at a table
level or do I have to make sure to call set synchronous_commit='off' every
