Re: Unknown winsock error 10061 - Mailing list pgsql-bugs

From Wojciech Strzałka
Subject Re: Unknown winsock error 10061
Date
Msg-id 1893954370.20090708142942@gmail.com
Whole thread Raw
In response to Re: Unknown winsock error 10061  (Dave Page <dpage@pgadmin.org>)
Responses Re: Unknown winsock error 10061  (Dave Page <dpage@pgadmin.org>)
List pgsql-bugs
And the result is:

2009-07-08 14:26:00 CEST PID:9612 DEBUG:  00000: forked new backend, pid=8120 socket=948
2009-07-08 14:26:00 CEST PID:9612 LOCATION:  BackendStartup, .\src\backend\postmaster\postmaster.c:3029
*** Finished restoring shared memory vars in restore_backend_variables (key=256, addr=02400000)
FATAL:  could not reattach to shared memory (key=256, addr=02400000): 487
2009-07-08 14:26:00 CEST PID:9612 DEBUG:  00000: reaping dead processes
2009-07-08 14:26:00 CEST PID:9612 LOCATION:  reaper, .\src\backend\postmaster\postmaster.c:2184
2009-07-08 14:26:00 CEST PID:9612 DEBUG:  00000: server process (PID 8120) exited with exit code 1
2009-07-08 14:26:00 CEST PID:9612 LOCATION:  LogChildExit, .\src\backend\postmaster\postmaster.c:2653
2009-07-08 14:26:01 CEST PID:9612 DEBUG:  00000: forked new backend, pid=9952 socket=948
2009-07-08 14:26:01 CEST PID:9612 LOCATION:  BackendStartup, .\src\backend\postmaster\postmaster.c:3029
*** Finished restoring shared memory vars in restore_backend_variables (key=256, addr=02400000)
*** Finished reattaching shared memory segment in PGSharedMemoryReAttach (key=256, addr=02400000)
2009-07-08 14:26:01 CEST PID:9952 DEBUG:  00000: postgres child[9952]: starting with (
2009-07-08 14:26:01 CEST PID:9952 LOCATION:  BackendRun, .\src\backend\postmaster\postmaster.c:3384
2009-07-08 14:26:01 CEST PID:9952 DEBUG:  00000:        postgres
2009-07-08 14:26:01 CEST PID:9952 LOCATION:  BackendRun, .\src\backend\postmaster\postmaster.c:3387
2009-07-08 14:26:01 CEST PID:9952 DEBUG:  00000:        -v196608
2009-07-08 14:26:01 CEST PID:9952 LOCATION:  BackendRun, .\src\backend\postmaster\postmaster.c:3387
2009-07-08 14:26:01 CEST PID:9952 DEBUG:  00000:        -y
2009-07-08 14:26:01 CEST PID:9952 LOCATION:  BackendRun, .\src\backend\postmaster\postmaster.c:3387
2009-07-08 14:26:01 CEST PID:9952 DEBUG:  00000:        masterdb
2009-07-08 14:26:01 CEST PID:9952 LOCATION:  BackendRun, .\src\backend\postmaster\postmaster.c:3387
2009-07-08 14:26:01 CEST PID:9952 DEBUG:  00000: )
2009-07-08 14:26:01 CEST PID:9952 LOCATION:  BackendRun, .\src\backend\postmaster\postmaster.c:3389
2009-07-08 14:26:01 CEST PID:9952 DEBUG:  00000: InitPostgres
2009-07-08 14:26:01 CEST PID:9952 LOCATION:  PostgresMain, .\src\backend\tcop\postgres.c:3333
2009-07-08 14:26:01 CEST PID:9952 DEBUG:  00000: my backend id is 5
2009-07-08 14:26:01 CEST PID:9952 LOCATION:  SharedInvalBackendInit, .\src\backend\storage\ipc\sinvaladt.c:316
2009-07-08 14:26:01 CEST PID:9952 DEBUG:  00000: StartTransaction
2009-07-08 14:26:01 CEST PID:9952 LOCATION:  ShowTransactionState, .\src\backend\access\transam\xact.c:4073
2009-07-08 14:26:01 CEST PID:9952 DEBUG:  00000: name: unnamed; blockState:       DEFAULT; state: INPROGR,
xid/subid/cid:0/1/0, nestlvl: 1, children:  
2009-07-08 14:26:01 CEST PID:9952 LOCATION:  ShowTransactionStateRec, .\src\backend\access\transam\xact.c:4111
2009-07-08 14:26:01 CEST PID:9952 DEBUG:  00000: CommitTransaction
2009-07-08 14:26:01 CEST PID:9952 LOCATION:  ShowTransactionState, .\src\backend\access\transam\xact.c:4073
2009-07-08 14:26:01 CEST PID:9952 DEBUG:  00000: name: unnamed; blockState:       STARTED; state: INPROGR,
xid/subid/cid:0/1/0, nestlvl: 1, children:  
2009-07-08 14:26:01 CEST PID:9952 LOCATION:  ShowTransactionStateRec, .\src\backend\access\transam\xact.c:4111
2009-07-08 14:26:01 CEST PID:9952 DEBUG:  00000: parse <unnamed>: SHOW TRANSACTION ISOLATION LEVEL
2009-07-08 14:26:01 CEST PID:9952 LOCATION:  exec_parse_message, .\src\backend\tcop\postgres.c:1117
2009-07-08 14:26:01 CEST PID:9952 STATEMENT:  SHOW TRANSACTION ISOLATION LEVEL



--
Pozdrowienia,Wojciech Strzałka



pgsql-bugs by date:

Previous
From: Wojciech Strzałka
Date:
Subject: Re: Unknown winsock error 10061
Next
From: Tsutomu Yamada
Date:
Subject: Re: Unknown winsock error 10061