From: | Andrew - Supernews <andrew+nonews(at)supernews(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: initdb fails on ultra2 sparc64, freebsd 5.4 |
Date: | 2005-05-21 05:05:34 |
Message-ID: | slrnd8tgcu.1feb.andrew+nonews@trinity.supernews.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 2005-05-21, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Andrew - Supernews <andrew+nonews(at)supernews(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-05-21 05:16:44 | Re: initdb fails on ultra2 sparc64, freebsd 5.4 |
Previous Message | Tom Lane | 2005-05-21 04:51:44 | Re: initdb fails on ultra2 sparc64, freebsd 5.4 |