From: | Andreas Kretschmer <akretschmer(at)spamfence(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: asynchronous commit |
Date: | 2015-01-19 19:10:15 |
Message-ID: | 20150119191015.GA23643@tux |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Robert DiFalco <robert(dot)difalco(at)gmail(dot)com> 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 call set synchronous_commit='off' every time I insert or
> update to them? And presumably remember to turn it back on again for safety.
I think, you can use unlogged tables instead.
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 | Robert DiFalco | 2015-01-19 19:25:57 | Re: asynchronous commit |
Previous Message | Jeff Janes | 2015-01-19 18:59:59 | Re: asynchronous commit |