Search Postgresql Archives

Re: asynchronous commit

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

 



On Mon, Jan 19, 2015 at 10:03 AM, Robert DiFalco <robert.difalco@xxxxxxxxx> 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. 

There is no clean way to do what you want currently.  You have to do the bookkeeping yourself.  There was discussion about adding an option for "asynchronous commit" to tables.  Then if all the tables changed during a transaction were asynchronous (and a few other conditions were met), the commit would automatically be asynchronous as well.  I'd like to see that, but I don't think anyone is actively working on implementing it.

Cheers,

Jeff

[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