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

Re: odd output in initdb

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: odd output in initdb
Date: 2010-01-31 17:24:39
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Sun, Jan 31, 2010 at 17:56, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> On Fri, Jan 29, 2010 at 23:28, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>>>>   initializing dependencies ... WARNING:  pgstat wait timeout
>> I'm not claiming it's not, but what exactly points to that? Does the
>> problem go away if you move to a version before that?
>> Because I'm 99% sure I saw it well before that commit, and we've had
>> reports on it from 8.4 as well, I'm not so sure... But it may be that
>> that commit made something more likely to happen...
> I notice pgstat_send is still using "if (pgStatSock < 0)" to detect

That's certainly so, but that shouldn't have any effect on this -
since on that platform it's defined to -1 anyway. But I'll go ahead
and fix it :-)

 Magnus Hagander

In response to


pgsql-hackers by date

Next:From: Magnus HaganderDate: 2010-01-31 17:27:59
Subject: Re: HS/SR and smart shutdown
Previous:From: Magnus HaganderDate: 2010-01-31 17:18:43
Subject: Re: pg_listener entries deleted under heavy NOTIFY load only on Windows

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