The following bug has been logged online:

Bug reference: 1074
Logged by: Neeraj K Sharma

Email address: neerajk_s (AT) yahoo (DOT) com

PostgreSQL version: 7.4

Operating system: linux 7.3.4

Description: postgresql crashes

Details:

I was running a test that initially insert 500 records
in a table, then it deletes 50 records, and insert 50 records every second
by different threads, and so it maintains aprox. 450 records every point of
time.
The database cores with the following message printed on screen.
WARNING: specified item offset is too large
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the
current transaction and exit, because another server process exited
abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and
repeat
your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the
current transaction and exit, because another server process exited
abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and
repeat
your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the
current transaction and exit, because another server process exited
abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and
repeat
your command.
Abort
Abort

I have seen this crash occurring every time, I run the test. Some time
database crashes with in 2-6 hrs, and some time it crashes after 15 hrs.

Please acquaint me what should I do in order to fix this problem. Write me
an email if want more information.

Neeraj K Sharma
Arroyo Video Solutions



---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

"PostgreSQL Bugs List" <pgsql-bugs (AT) postgresql (DOT) org> writes:
Hmm. AFAICS this should always be followed by an ERROR message. There
are at least two issues here: why does this message occur, and why does
a crash follow instead of more-graceful error recovery?

Does any additional information show up in the postmaster log?

Could you provide your test program? Could you provide a stack trace
from the backend core dump?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend