On Wed, Jun 6, 2012 at 5:41 PM, Jim Nasby j...@nasby.net wrote:
On 5/30/12 4:42 PM, Ants Aasma wrote:
I was thinking about what is the earliest time where we could set hint
bits. This would be just after the commit has been made visible.
Except that's only true when there are no other
On Wed, Jun 6, 2012 at 6:41 PM, Jim Nasby j...@nasby.net wrote:
Except that's only true when there are no other transactions running. That's
been one of the big sticking points about trying to proactively set hint
bits; in a real system you're not going to gain very much unless you wait a
On 5/30/12 4:42 PM, Ants Aasma wrote:
I was thinking about what is the earliest time where we could set hint
bits. This would be just after the commit has been made visible.
Except that's only true when there are no other transactions running. That's
been one of the big sticking points about
I was thinking about what is the earliest time where we could set hint
bits. This would be just after the commit has been made visible. When
the transaction completes and commit confirmation is sent to the
client the backend will usually go to sleep waiting on the network
socket waiting for
On Wed, May 30, 2012 at 4:42 PM, Ants Aasma a...@cybertec.at wrote:
I was thinking about what is the earliest time where we could set hint
bits. This would be just after the commit has been made visible. When
the transaction completes and commit confirmation is sent to the
client the backend
On Thu, May 31, 2012 at 1:01 AM, Merlin Moncure mmonc...@gmail.com wrote:
I think this is a really neat idea, and could solve a lot of problems.
Since you don't have to do any clog checks (you know when you commit)
-- i think it's a win all around -- so much so that it might be worth
seeing
