From: | Vadim Mikheev <vadim(at)krs(dot)ru> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Developers List <hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] why do shmem attach? |
Date: | 1999-09-20 14:12:28 |
Message-ID: | 37E640CC.5AC9C432@krs.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
>
> Vadim Mikheev <vadim(at)krs(dot)ru> writes:
> > 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).
>
> Have I got a deal for you ;-). I have uncommitted changes that add
> a pointer (SHMEM_OFFSET that is) to each backend's PROC struct into
> the per-backend info array that already existed in shmem.c. The
> routines in shmem.c that searched for PROC structures are now in
> sinval.c, and just do a simple scan of the ProcState array to find
> the PROC structs. They should be a whole lot faster --- which is
> good since these things run with spinlocks held...
Nice. I have new member for PROC that should be searched
sometime -:)
Vadim
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1999-09-20 14:13:48 | Re: [HACKERS] why do shmem attach? |
Previous Message | Bruce Momjian | 1999-09-20 14:12:04 | Re: [HACKERS] Status on Jan Wieck |