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

From Andrew Dunstan
Subject Re: odd output in initdb
Date
Msg-id 4B662ABC.8010407@dunslane.net
Whole thread Raw
In response to Re: odd output in initdb  (Magnus Hagander <magnus@hagander.net>)
Responses Re: odd output in initdb
List pgsql-hackers

Magnus Hagander wrote:
>>
>> 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...
>   


The buildfarm logs say otherwise. This was first seen in Jan 10, at 
least on my Windows animals:
   pgbfprod=# select sysname, min(snapshot) from build_status_log where   sysname ~ 'bat' and log_stage ~ 'initdb' and
log_text~ 'pgstat'   group by sysname;    sysname  |         min           ----------+---------------------    dawn_bat
|2010-01-10 17:30:02    red_bat  | 2010-01-10 23:30:01   (2 rows)
 

cheers

andrew




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Aggressive freezing versus caching of pg_proc entries
Next
From: "HX Zheng"
Date:
Subject: contrib\xml2 package's xpath_table function in PostgreSQL