Shawn Garbett <shawn_garbett@yahoo.com> writes:
> I've got C code written to store a value in the
> context of an active connection using a hash. It
> worked until I added some semaphores to control memory
> reads/writes to the shared resource. This is on SLES9
> Linux box running a 2.6.5 kernel.
I dunno about your shared library problem, but there is nothing even
remotely "shared" about that hashtable, so you hardly need a semaphore
to protect it. It's just in the memory of one backend process.
regards, tom lane