Claudio Natoli <claudio.natoli@memetrics.com> writes:
> So this means we'll have to pull relHash out of the shared FreeSpaceMap
> structure and make it a variable in it's own right?
Hm. The freespace.c code is relatively new and might not be jumping
through all of the hoops it should be jumping through. My recollection
of the older code is that the logic was like "create or attach to shared
memory structure named 'foo', if not create then initialize the shared
structure". I'll take the blame if freespace.c doesn't do this right...
> [Same goes for lockHash and proclockHash in the LockMethod structure
> reference by "LockTable (lock method table)"]
The lock code *should* be doing this right, unless I've totally
forgotten the modification history ...
regards, tom lane