Re: initdb fails on ultra2 sparc64, freebsd 5.4
От | Andrew - Supernews |
---|---|
Тема | Re: initdb fails on ultra2 sparc64, freebsd 5.4 |
Дата | |
Msg-id | slrnd8tgcu.1feb.andrew+nonews@trinity.supernews.net обсуждение исходный текст |
Ответ на | initdb fails on ultra2 sparc64, freebsd 5.4 (David Walker <david@cosmicfires.com>) |
Ответы |
Re: initdb fails on ultra2 sparc64, freebsd 5.4
|
Список | pgsql-bugs |
On 2005-05-21, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Andrew - Supernews <andrew+nonews@supernews.com> writes: >> The reason for the hang is that the sending end of the pipe from initdb >> to postgres is not being closed by popen(), so postgres never sees EOF >> on it. In this context I am suspicious of the fact that while libpq is >> being built with threading, the apps which link against it do not appear >> to be. > > initdb does not use libpq ... it might link to it, because of sloppy > LIBS list management, but it doesn't ever call it. There is, by > definition, no running postmaster available for libpq to contact. Linking to it is enough to bring in libc_r, and pick up libc_r's versions of at least some system calls. The ktrace results show this. -- Andrew, Supernews http://www.supernews.com - individual and corporate NNTP services
В списке pgsql-bugs по дате отправления: