Server process exited with unexpected status 128. - Mailing list pgsql-hackers

Hello pgsql-hackers,

When I try to execute the next SQL statement, sever was crashed:
DELETE FROM ma_data WHERE id in (-1,212803,..... );... - is 500k text like id separated by ",". Its about 100000
values.
Run from pgplsql function, like EXECUTE st;.
postgresql-2005-09-25_000000.log:

2005-09-26 15:45:52 LOG:  server process (PID 2040) exited with unexpected status 128
2005-09-26 15:45:52 LOG:  terminating any other active server processes
2005-09-26 15:45:52 WARNING:  terminating connection because of crash of another server process
2005-09-26 15:45:52 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.
 
2005-09-26 15:45:52 HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2005-09-26 15:45:52 WARNING:  terminating connection because of crash of another server process
2005-09-26 15:45:52 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.
 
2005-09-26 15:45:52 HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2005-09-26 15:45:52 WARNING:  terminating connection because of crash of another server process
2005-09-26 15:45:52 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.
 
2005-09-26 15:45:52 HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2005-09-26 15:45:52 LOG:  all server processes terminated; reinitializing
2005-09-26 15:45:52 LOG:  database system was interrupted at 2005-09-26 15:45:48 FLE Daylight Time
2005-09-26 15:45:52 LOG:  checkpoint record is at 1/1720CF88
2005-09-26 15:45:52 LOG:  redo record is at 1/17008C80; undo record is at 0/0; shutdown FALSE
2005-09-26 15:45:52 LOG:  next transaction ID: 40476; next OID: 1836657
2005-09-26 15:45:52 LOG:  next MultiXactId: 102; next MultiXactOffset: 202
2005-09-26 15:45:52 LOG:  database system was not properly shut down; automatic recovery in progress
2005-09-26 15:45:52 LOG:  redo starts at 1/17008C80
2005-09-26 15:45:53 LOG:  unexpected pageaddr 1/11A7C000 in log file 1, segment 24, offset 10993664
2005-09-26 15:45:53 LOG:  redo done at 1/18A7AA08
2005-09-26 15:46:02 LOG:  database system is ready



#---------------------------------------------------------------------------
# RESOURCE USAGE (except WAL)
#---------------------------------------------------------------------------

# - Memory -
shared_buffers = 8000                   # min 16 or max_connections*2, 8KB each
temp_buffers = 10000                    # min 100, 8KB each
#max_prepared_transactions = 5          # can be 0 or more
# note: increasing max_prepared_transactions costs ~600 bytes of shared memory
# per transaction slot, plus lock space (see max_locks_per_transaction).
work_mem = 200000                       # min 64, size in KB
maintenance_work_mem = 65536            # min 1024, size in KB
max_stack_depth = 65536                 # min 100, size in KB

PG 8.1beta2 WIN32.

-- 
С наилучшими пожеланиями, Репко Андрей Владимирович       mailto:repko@sart.must-ipra.com