Re: testing HS/SR - 1 vs 2 performance
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Simon Riggs <simon@2ndQuadrant.com>
Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, Erik Rijkers <er@xs4all.nl>, pgsql-hackers@postgresql.org
Date: 2010-04-17T19:45:47Z
Lists: pgsql-hackers
Simon Riggs <simon@2ndQuadrant.com> writes: > On Sat, 2010-04-17 at 11:13 -0400, Tom Lane wrote: >> It'd be cheaper anyway to sort and search the >> array using plain <, so why are you so eager to use >> TransactionIdFollows? > The array grows to the right and is laid out one xid per element, > resulting in a sequence of values that are transactionid-monotonic. How do you know that just adding items at the right will produce a sorted array? It seems quite unlikely to me that transactions can be guaranteed to arrive at this code in XID order. I think you need to do an explicitly sorted insertion. > ... Doing it this way means that we can > add rows past the head of the array and then move the head atomically, > so that we can make adding xids lock-free. ... and even without that issue, this seems like utter fantasy. How are you going to do that "atomically"? Have you considered what will happen on weak-memory-ordering machines like PPC, in particular? regards, tom lane