Andrew Dunstan <[EMAIL PROTECTED]> writes: > Tom Lane wrote: >> One idea that comes to mind is a DNS lookup timeout. Can you strace the >> postmaster to see what it's doing?
> There is ktrace output I managed to capture at > http://developer.postgresql.org/~adunstan/ktrace.txt > Not sure what it tells us. I do see it reading in the whole timezone db, > which isn't pretty. Yeah... I think we fixed that in 8.1. Anyway, the tail end of the trace shows it repeatedly sending off a UDP packet and getting practically the same data back: 24583 postgres CALL socket(0x2,0x2,0) 24583 postgres RET socket 3 24583 postgres CALL sendto(0x3,0x43e1e000,0x25,0,0x493a6338,0x10) 24583 postgres GIO fd 3 wrote 37 bytes "\M-Sr\^A\0\0\^A\0\0\0\0\0\0\^B''\rkaltenbrunner\^Bcc\0\0\^A\0\^A" 24583 postgres RET sendto 37/0x25 24583 postgres CALL getpid() 24583 postgres RET getpid 24583/0x6007 24583 postgres CALL select(0x4,0x40739600,0,0,0xfffffffffffe4d90) 24583 postgres RET select 1 24583 postgres CALL recvfrom(0x3,0x477e4000,0x10000,0,0xfffffffffffe4da0,0xfffffffffffe4d5c) 24583 postgres GIO fd 3 read 37 bytes "\M-Sr\M^A\M^B\0\^A\0\0\0\0\0\0\^B''\rkaltenbrunner\^Bcc\0\0\^A\0\^A" 24583 postgres RET recvfrom 37/0x25 24583 postgres CALL close(0x3) 24583 postgres RET close 0 I'm not too up on what the DNS protocol looks like on-the-wire, but I'll bet this is it. I think it's trying to look up "kaltenbrunner.cc" and failing. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
