Josh Berkus <[EMAIL PROTECTED]> writes:
> One thing I've not seen an answer to: does Postgres run acceptably on other
> people's Solaris boxes? If this bug is preventing running on Solaris at
> all, I'd say fix it ... Solaris is a major platform. If it only affects
> users of one particular
Tom,
> Too bad we didn't figure this out yesterday. We are now in code freeze
> for 7.4 release, and I'm hesitant to apply a fix for what is arguably a
> broken platform. Core guys, time for a vote ... do we fix, or hold this
> for 7.4.1?
One thing I've not seen an answer to: does Postgres run
Kurt Roeckx <[EMAIL PROTECTED]> writes:
> So the for loop over the addresses that are returned should go
> over both socket() and bind() instead of only socket(). And
> probably connect() too.
> The code now assumes if you create a socket of a certain type you
> can actually use it.
Ah, light daw
On Thu, Nov 13, 2003 at 04:04:23PM -0500, Derek Morr wrote:
>
> the
> machine I'm using (a V880 running 2.8) has no IPv6 address on any of its
> interfaces.
So the for loop over the addresses that are returned should go
over both socket() and bind() instead of only socket(). And
probably conne
I think I have some more information on the statistics collector startup
problem on Solaris.
I inserted the following into pgstat.c:
if (bind(pgStatSock, addr->ai_addr, addr->ai_addrlen) < 0)
{
/* what type of socket are we trying to bind? */
fprintf(stderr, "Address family is %d\n",
Thanks to Tom Lane, Kurt Roeckx, Zeugswetter Andreas and Shigehiro.
It was solved. It reports.
On Thu, 13 Nov 2003 09:50:59 -0500 Tom Lane <[EMAIL PROTECTED]> wrote:
>
> Hmm ... that's certainly evidence that "localhost" will resolve
> correctly on your machine, but then why is the bind() faili
Kiyoshi Sawada <[EMAIL PROTECTED]> writes:
> $ /usr/local/bin/nslookup localhost
> Note: nslookup is deprecated and may be removed from future releases.
> Consider using the `dig' or `host' programs instead. Run nslookup with
> the `-sil[ent]' option to prevent this message from appearing.
> Serv
On Thu, 13 Nov 2003 11:39:49 +0900 Kiyoshi Sawada <[EMAIL PROTECTED]> wrote:
> $ nslookup localhost
> Server: name.server.mydomain
> Address: xxx.xx.xx.xxx
> : : :
> (failed test)
> Is it necessary to start a DNS server to bind 'localhost' in Kiyoshi's machine?
>
I got bind-9.2.2-sol8-intel-
On Wed, 12 Nov 2003 13:46:52 -0500 Tom Lane <[EMAIL PROTECTED]> wrote:
> Kurt Roeckx <[EMAIL PROTECTED]> writes:
> > It's always a good idea to put localhost into dns too.
>
> Yeah, but "localhost" *is* resolving as something on Kiyoshi's
> machine, else a different error message would have appe
Kurt Roeckx <[EMAIL PROTECTED]> writes:
> It's always a good idea to put localhost into dns too.
Yeah, but "localhost" *is* resolving as something on Kiyoshi's
machine, else a different error message would have appeared.
I'm wondering just what it resolved to though --- maybe we should
have made
On Wed, Nov 12, 2003 at 10:32:38AM -0500, Tom Lane wrote:
> "Zeugswetter Andreas SB SD" <[EMAIL PROTECTED]> writes:
> > Are we using an api that only returns nslookup responses and not
> > /etc/hosts entries ? At least on AIX it looks like it.
>
> We use getaddrinfo(), or if that doesn't exist get
"Zeugswetter Andreas SB SD" <[EMAIL PROTECTED]> writes:
> Are we using an api that only returns nslookup responses and not
> /etc/hosts entries ? At least on AIX it looks like it.
We use getaddrinfo(), or if that doesn't exist gethostbyname().
If there's a problem of that ilk then it's those libra
> > LOG: could not bind socket for statistics collector: Cannot assign requested
> > address
>
> Hmm ... that's sure the problem, but what can we do about it? ISTM that
> any non-broken system ought to be able to resolve "localhost". Actually
> it's worse than that: your system resolved "local
Kiyoshi Sawada <[EMAIL PROTECTED]> writes:
> On Tue, 11 Nov 2003 09:18:48 -0500 Tom Lane <[EMAIL PROTECTED]> wrote:
>> So why not? Try looking in the postmaster log for errors related to
>> stats collector startup. (pstat is irrelevant, btw.)
> LOG: could not bind socket for statistics collect
Dear Tom Lane.
On Tue, 11 Nov 2003 09:18:48 -0500 Tom Lane <[EMAIL PROTECTED]> wrote:
> Kiyoshi Sawada <[EMAIL PROTECTED]> writes:
> > 2. Regression Failur stats . FAILED .
> > 3. Not running stats buffer process and stats collector process.
>
> So why not? Try looking in the postmaster l
Kiyoshi Sawada <[EMAIL PROTECTED]> writes:
> 2. Regression Failur stats . FAILED .
> 3. Not running stats buffer process and stats collector process.
So why not? Try looking in the postmaster log for errors related to
stats collector startup. (pstat is irrelevant, btw.)
Failed to build on Solaris.
Summary
1. Checking for pstat... no
2. Regression Failur stats . FAILED .
3. Not running stats buffer process and stats collector process.
Environments
SunOS 5.8 Generic_108528-15 sun4m sparc
SunOS 5.8 Generic_108
17 matches
Mail list logo
