Re: [COMMITTERS] pgsql: Fix TransactionIdIsCurrentTransactionId() to use binary search
От | Robert Treat |
---|---|
Тема | Re: [COMMITTERS] pgsql: Fix TransactionIdIsCurrentTransactionId() to use binary search |
Дата | |
Msg-id | 200803271656.45574.xzilla@users.sourceforge.net обсуждение исходный текст |
Ответы |
Re: [COMMITTERS] pgsql: Fix TransactionIdIsCurrentTransactionId() to use binary search
|
Список | pgsql-hackers |
On Sunday 16 March 2008 22:18, Tom Lane wrote: > Log Message: > ----------- > Fix TransactionIdIsCurrentTransactionId() to use binary search instead of > linear search when checking child-transaction XIDs. This makes for an > important speedup in transactions that have large numbers of children, > as in a recent example from Craig Ringer. We can also get rid of an > ugly kluge that represented lists of TransactionIds as lists of OIDs. > Are there any plans to backpatch this into REL8_3_STABLE? It looks like I am hitting a pretty serious performance regression on 8.3 with a stored procedure that grabs a pretty big recordset, and loops through doing insert....update on unique failures. The procedure get progressivly slower the more records involved... and dbx shows me stuck in TransactionIdIsCurrentTransactionId(). I can provide provide more details if needed (lmk what your looking for) but it certainly looks like the issue discussed here: http://archives.postgresql.org/pgsql-performance/2008-03/msg00191.php -- Robert Treat Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
В списке pgsql-hackers по дате отправления: