Re: [HACKERS] odd output in initdb

2010-02-01 Thread Andrew Dunstan
Magnus Hagander wrote: Did those two members produce consistent issues? Can you give them a couple of kicks to get enough buidls out of them to figure out if this solved the problem? Not very easily. I am currently travelling. It was happening fairly consistently on red_bat and seems to

Re: [HACKERS] odd output in initdb

2010-02-01 Thread Magnus Hagander
2010/2/1 Andrew Dunstan : > > Magnus Hagander wrote: >>> >>> Actually, on close inspection it looks to me like this commit: "Create >>> typedef pgsocket for storing socket descriptors." >>> >>> c

Re: [HACKERS] odd output in initdb

2010-01-31 Thread Andrew Dunstan
Magnus Hagander wrote: Actually, on close inspection it looks to me like this commit: "Create typedef pgsocket for storing socket descriptors." could well be the culprit. I'm not cla

Re: [HACKERS] odd output in initdb

2010-01-31 Thread Magnus Hagander
On Sun, Jan 31, 2010 at 18:33, Tom Lane wrote: > Magnus Hagander writes: >> On Sun, Jan 31, 2010 at 17:56, Tom Lane wrote: >>> I notice pgstat_send is still using "if (pgStatSock < 0)" to detect >>> PGINVALID_SOCKET ... > >> That's certainly so, but that shouldn't have any effect on this - >> si

Re: [HACKERS] odd output in initdb

2010-01-31 Thread Tom Lane
Magnus Hagander writes: > On Sun, Jan 31, 2010 at 17:56, Tom Lane wrote: >> I notice pgstat_send is still using "if (pgStatSock < 0)" to detect >> PGINVALID_SOCKET ... > 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

Re: [HACKERS] odd output in initdb

2010-01-31 Thread Magnus Hagander
On Sun, Jan 31, 2010 at 17:56, Tom Lane wrote: > Magnus Hagander writes: >> On Fri, Jan 29, 2010 at 23:28, Andrew Dunstan 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

Re: [HACKERS] odd output in initdb

2010-01-31 Thread Tom Lane
Magnus Hagander writes: > On Fri, Jan 29, 2010 at 23:28, Andrew Dunstan 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

Re: [HACKERS] odd output in initdb

2010-01-31 Thread Magnus Hagander
On Fri, Jan 29, 2010 at 23:28, Andrew Dunstan 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 timeou

Re: [HACKERS] odd output in initdb

2010-01-29 Thread Andrew Dunstan
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

[HACKERS] odd output in initdb

2010-01-29 Thread Andrew Dunstan
I saw some odd pgstat output during an initdb on Windows today: The files belonging to this database system will be owned by user "pgrunner". This user must also own the server process. The database cluster will be initialized with locale C. The default database encoding has acco