On 16/10/2014 7:59 AM, Robert Haas wrote:
On Thu, Oct 16, 2014 at 9:30 AM, Andres Freund wrote:
On 2014-10-16 09:19:16 -0400, Robert Haas wrote:
On Thu, Oct 16, 2014 at 8:03 AM, Ryan Johnson
wrote:
Why not use an RCU mechanism [1] and ditch the hazard pointers? Seems like
an ideal fit
On 16/10/2014 7:19 AM, Robert Haas wrote:
On Thu, Oct 16, 2014 at 8:03 AM, Ryan Johnson
wrote:
Why not use an RCU mechanism [1] and ditch the hazard pointers? Seems like
an ideal fit...
In brief, RCU has the following requirements:
Read-heavy access pattern
Writers must be able to make dead
On 15/10/2014 11:41 AM, Robert Haas wrote:
On Wed, Oct 15, 2014 at 2:03 AM, Andres Freund wrote:
On 2014-10-14 17:53:10 -0400, Robert Haas wrote:
On Tue, Oct 14, 2014 at 4:42 PM, Andres Freund wrote:
The code in CHashSearch shows the problem there: you need to STORE the
hazard pointer before
On 15/10/2014 10:32 AM, Ants Aasma wrote:
On Tue, Oct 14, 2014 at 6:19 PM, Robert Haas wrote:
With regard for using a hash table for the buffer mapping lock I'm
doubtful that any form of separate chaining is the right one. We
currently have a quite noticeable problem with the number of cache
mi
On 27/06/2014 8:20 AM, Alvaro Herrera wrote:
Ryan Johnson wrote:
On 26/06/2014 11:04 PM, Alvaro Herrera wrote:
Ryan Johnson wrote:
As part of a research project, I'm trying to change Read Committed
isolation to use HeapTupleSatisfiesNow rather than acquiring a new
snapshot at every comma
On 27/06/2014 3:14 AM, Andres Freund wrote:
On 2014-06-26 22:47:47 -0600, Ryan Johnson wrote:
Hi,
As part of a research project, I'm trying to change Read Committed isolation
to use HeapTupleSatisfiesNow rather than acquiring a new snapshot at every
command [1]. Things appear to have
On 26/06/2014 11:04 PM, Alvaro Herrera wrote:
Ryan Johnson wrote:
As part of a research project, I'm trying to change Read Committed
isolation to use HeapTupleSatisfiesNow rather than acquiring a new
snapshot at every command [1].
Are you aware of this?
c
Hi,
As part of a research project, I'm trying to change Read Committed
isolation to use HeapTupleSatisfiesNow rather than acquiring a new
snapshot at every command [1]. Things appear to have gone reasonably
well so far, except certain queries fail with "ERROR: non-MVCC
snapshots are not supp
