Re: Examining the output of: ldd `which postgres`

Sean Chittenden wrote:
> > Backend only forks(). I think you would be better off using
> > Makefile macros to _remove_ those two libraries.
> >
> > I see this:
> >
> > $(filter crypt.o getaddrinfo.o inet_aton.o snprintf.o strerror.o path.o thread.o, $(LIBOBJS))
> >
> > Seems you need the reverse.
>
> Ah, well, if it fork()'s, then I don't really care. The best
> remaining argument for this would be to reduce the total size of a
> machine's VM page table size and possibly the expense of switching
> contexts between procs, but that's a pretty weak argument for only .5M
> of shared RAM. For some reason I thought it exec()'ed a child with
> the args necessary for it to read in a postgresql.conf. Looks like
> the comment in backend/storage/ipc/ipci.c is out of date then:
>
> * AttachSharedMemoryAndSemaphores
> * Attaches to the existing shared resources when exec()'d off
> * by the postmaster.

I have updated this comment.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073