why do shmem attach?

From: Vadim Mikheev <vadim(at)krs(dot)ru>
To: PostgreSQL Developers List <hackers(at)postgreSQL(dot)org>
Subject: why do shmem attach?
Date: 1999-09-20 03:35:25
Message-ID: 37E5AB7D.F8EA85D4@krs.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Exec-on-startup was removed by Bruce long time ago.
Why we still attach to shmem after fork?
Or shmem inheritance is not portable?
Also, all this ShmemIndex stuff seems to be useless
(except of backend PID lookup but it's for sure
should be in separate hash table).
And why separate shmem segment (!!!) is used for
Slocks (ipc.c:CreateAndInitSLockMemory(), etc) - they
use so small amount of memory!

Just wondering...
I'm going to use old shmem init code for WAL but would like
to denote that shmem stuff need in cleanup.

Vadim

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Robinson 1999-09-20 03:44:55 Re: [HACKERS] All things equal, we are still alot slower then MySQL?
Previous Message Thomas Lockhart 1999-09-20 03:06:48 Re: INSERT/DEFAULT VALUES broken?