Re: odd output in initdb

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: odd output in initdb
Date: 2010-01-31 16:33:44
Message-ID: 9837222c1001310833i13a83800o87670491ad7ae8c2@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jan 29, 2010 at 23:28, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
>
> Andrew Dunstan wrote:
>>
>>
>>   initializing dependencies ... WARNING:  pgstat wait timeout
>>   WARNING:  pgstat wait timeout
>>   ok
>>     vacuuming database template1 ... WARNING:  pgstat wait timeout
>>   WARNING:  pgstat wait timeout
>>   ok
>>   copying template1 to template0 ... WARNING:  pgstat wait timeout
>>
>>
>> I can't see an obvious culprit in the commit logs right off.
>
> Actually, on close inspection it looks to me like this commit: "Create
> typedef pgsocket for storing socket descriptors."
> <http://git.postgresql.org/gitweb?p=postgresql.git;a=commit;h=ea1a4463e9de9662b7c9e13374ec8c7b92ff2f19>
> could well be the culprit.

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...

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-01-31 16:35:49 Re: Using the new libpq connection functions in PostgreSQL binaries
Previous Message Dean Rasheed 2010-01-31 16:25:45 Re: Memory leak in deferrable index constraints