Search Postgresql Archives

Re: slow, long-running 'commit prepared'

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

 



On Tue, Nov 25, 2008 at 08:05:36PM -0800, John Smith wrote:
> Thanks for the quick response, Andrew. How could the 'commit prepared'
> be I/O bound? Isn't all the I/O accomplished during 'prepare
> transaction', leaving only a tiny bit of data to write at commit?

No.  When you do PREPARE TRANSACTION you have to save a whole lot of
state.  And when you then do COMMIT PREPARED, you say, "Lose that
state in favour of this new state."  All that work has to be done
again, in the other direction.

It's not for nothing that people think 2PC is a heavyweight and
expensive system. :-(

A


-- 
Andrew Sullivan
ajs@xxxxxxxxxxxxxxx

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[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