Re: backend reset of database

From: Geoffrey <esoteric(at)3times25(dot)net>
To: pgsql-general(at)postgresql(dot)org
Cc: Terry Lee Tucker <terry(at)leetuckert(dot)net>, John Allgood <john(at)turbocorp(dot)com>, "J(dot) D(dot) Pearson" <jpearson(at)turbocorp(dot)com>
Subject: Re: backend reset of database
Date: 2007-04-12 19:21:46
Message-ID: 461E86CA.5070203@3times25.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I've done some further research on this problem. I'm not a big user of
strace, so I'm looking at getting some insight here. Basically, there
are two different versions of the pcmiler libraries. One set works, the
other does not. The following is the strace output from both processes.
The first is the one that works, the second is the one that does not
work. Anyone see anything here that might identify the problem? Thanks:

working strace:

send(3, "Q\0\0\0008select pcm_getmiles_s(\'spar"..., 57, 0) = 57
rt_sigaction(SIGPIPE, {SIG_DFL}, {SIG_IGN}, 8) = 0
poll([{fd=3, events=POLLIN|POLLERR, revents=POLLIN}], 1, -1) = 1
recv(3, "T\0\0\0\'\0\1pcm_getmiles_s\0\0\0\0\0\0\0\0\0\2\275"..., 16384,
0) = 74ioctl(0, SNDCTL_TMR_TIMEBASE or TCGETS, {c_iflags=0x2d02,
c_oflags=0x5, c_cflags=0x4bf, c_lflags=0x8a3b, c_line=0,
c_cc="\x03\x1c\x7f\x15\x04\x00\x01\xff\x11\x13\x1a\xff\x12\x0f\x17\x16\xff\x00\x00"})
= 0
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {c_iflags=0x2d02, c_oflags=0x5,
c_cflags=0x4bf, c_lflags=0x8a3b, c_line=0,
c_cc="\x03\x1c\x7f\x15\x04\x00\x01\xff\x11\x13\x1a\xff\x12\x0f\x17\x16\xff\x00\x00"})
= 0
ioctl(1, TIOCGWINSZ, {ws_row=24, ws_col=80, ws_xpixel=0, ws_ypixel=0}) = 0

broken strace:

send(3, "Q\0\0\0008select pcm_getmiles_s(\'spar"..., 57, 0) = 57
rt_sigaction(SIGPIPE, {SIG_DFL}, {SIG_IGN}, 8) = 0
poll([{fd=3, events=POLLIN|POLLERR, revents=POLLIN|POLLHUP}], 1, -1) = 1
recv(3, "", 16384, 0) = 0
time(NULL) = 1176403599
poll([{fd=3, events=POLLIN|POLLERR, revents=POLLIN|POLLHUP}], 1, 0) = 1
recv(3, "", 16384, 0) = 0
close(3) = 0
write(2, "server closed the connection une"..., 137server closed the
connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
) = 137
write(2, "The connection to the server was"..., 57The connection to the
server was lost. Attempting reset: ) = 57

--
Until later, Geoffrey

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
- Benjamin Franklin

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Geoffrey 2007-04-12 19:38:37 Re: backend reset of database
Previous Message Benjamin Arai 2007-04-12 19:20:57 pg_dump when database contains multiple tablespaces