Postgres Pro
Downloads
Home   >   mailing lists

Re: odd output in initdb - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: odd output in initdb
Date
Msg-id 9837222c1001310833i13a83800o87670491ad7ae8c2@mail.gmail.com
Whole thread Raw
In response to Re: odd output in initdb  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: odd output in initdb  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: odd output in initdb  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Tree view 
On Fri, Jan 29, 2010 at 23:28, Andrew Dunstan <andrew@dunslane.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 HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/

pgsql-hackers by date:

Previous
From: Dean Rasheed
Date:
Subject: Re: Memory leak in deferrable index constraints
Next
From: Tom Lane
Date:
Subject: Re: Using the new libpq connection functions in PostgreSQL binaries