Skip site navigation (1) Skip section navigation (2)

Re: initdb fails on ultra2 sparc64, freebsd 5.4

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: andrew(at)supernews(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: initdb fails on ultra2 sparc64, freebsd 5.4
Date: 2005-05-21 04:51:44
Message-ID: 6228.1116651104@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
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.

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Andrew - SupernewsDate: 2005-05-21 05:05:34
Subject: Re: initdb fails on ultra2 sparc64, freebsd 5.4
Previous:From: Andrew - SupernewsDate: 2005-05-21 04:30:06
Subject: Re: initdb fails on ultra2 sparc64, freebsd 5.4

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group