From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Robert DiFalco <robert(dot)difalco(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: asynchronous commit |
Date: | 2015-01-19 18:59:59 |
Message-ID: | CAMkU=1wNDY4b6CqabVuP-jkcNKg9uV=8-Tasv=yhOpDVsNnBcw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Jan 19, 2015 at 10:03 AM, 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.
>
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
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Kretschmer | 2015-01-19 19:10:15 | Re: asynchronous commit |
Previous Message | Robert DiFalco | 2015-01-19 18:03:19 | asynchronous commit |