Re: [HACKERS] Release Notes Overview
Gregory Stark wrote: > > "Simon Riggs" <[EMAIL PROTECTED]> writes: > > > Asynchronous Commit allows some transactions to commit faster than > > others, offering a trade-off between performance and durability for > > specific transaction types only > > A lot of users will be confused about what asynchronous commit does. I think > it's important to be consistently precise when describing it. > > It doesn't allow commits to be any faster, what it does is "allow clients to > start a new transaction and continue working without waiting for their > previous commit to complete". Saying something like "This allows high volumes > of short transactions such as typical web sites to run more efficiently and > with fewer connections" might also help clarify the use case it helps. Well, logically the commit does happen faster in that your transaction and others see the commit. It is just durability that is delayed. -- Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
Re: [HACKERS] Release Notes Overview
On Fri, 2007-10-05 at 11:24 +0100, Gregory Stark wrote: > "Simon Riggs" <[EMAIL PROTECTED]> writes: > > > Asynchronous Commit allows some transactions to commit faster than > > others, offering a trade-off between performance and durability for > > specific transaction types only > > A lot of users will be confused about what asynchronous commit does. I think > it's important to be consistently precise when describing it. > > It doesn't allow commits to be any faster, what it does is "allow clients to > start a new transaction and continue working without waiting for their > previous commit to complete". Saying something like "This allows high volumes > of short transactions such as typical web sites to run more efficiently and > with fewer connections" might also help clarify the use case it helps. The general shape of the overview was what I was looking at. I agree with your specific comment. -- Simon Riggs 2ndQuadrant http://www.2ndQuadrant.com ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] Release Notes Overview
"Simon Riggs" <[EMAIL PROTECTED]> writes: > Asynchronous Commit allows some transactions to commit faster than > others, offering a trade-off between performance and durability for > specific transaction types only A lot of users will be confused about what asynchronous commit does. I think it's important to be consistently precise when describing it. It doesn't allow commits to be any faster, what it does is "allow clients to start a new transaction and continue working without waiting for their previous commit to complete". Saying something like "This allows high volumes of short transactions such as typical web sites to run more efficiently and with fewer connections" might also help clarify the use case it helps. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
