PANIC: hash table "Shared Buffer Lookup Table" corrupted

All,

Just started an upgrade from 7.2.X to 7.4.2. I am getting the following PANIC when loading the data from a 7.2.4 db 
using 7.4.2 pg_dump via a pipe 

pg_dump -h bda4c OLD_DB |psql -h bda5 -e NEW_DB

bda4c is    PostgreSQL 7.2.4 on i686-pc-linux-gnu, compiled by GCC 2.95.4
bda5  is    PostgreSQL 7.4.2 on i686-pc-linux-gnu, compiled by GCC 2.95.4

both systems are debian 3 with updates but Postgresql was compiled from source.

I stopped and started the postmaster and am still getting this.  any ideas?

The system has been loading data (via INSERTS) for days (93936795 rows 10 tables) with no problem.  This is my first 
try at copy.

Thanks
Jim


2004-03-23 21:56:48 [6868] PANIC:  hash table "Shared Buffer Lookup Table" corrupted
CONTEXT:  COPY emi_110101, line 26679: "18860   A-9417-7011-044-89      200304  110101  2003-03-28      0       00000
00000   000     10      3056217468      2       0501    0222    5       0       0       0..."
STATEMENT:  COPY emi_110101 (df_id, bi_billing_number, mdf_id, recid, message_date, from_number_len, from_number, ove
rflow_digits, to_number_len, to_number, orig_term_id, fgd_tgn, carrier_id, access_method, routing_method, dialing_met
hod, ani, ncta, connect_time, billable_time, method_of_rec, from_rac, local_co_info, type_of_service, method_of_signa
ling, indicator_1, indicator_2, indicator_3, indicator_4, indicator_5, indicator_6, indicator_7, indicator_8, indicat
or_9, indicator_10, indicator_11, indicator_12, indicator_13, indicator_14, indicator_15, indicator_16,
indicator_17,indicator_18,indicator_19, indicator_20, opr_unit, rec_pt_id, bill_rac_rao, indicator_21, indicator_22,
indicator_2
3, indicator_24, indicator_25, indicator_26, indicator_27, indicator_28, indicator_29, indicator_30, bill_number, nec
a_company_code, fgd_call_event_status, fg_id_code, toll_library_code, toll_settlement, conversion_time, orig_lrn, ori
g_ocn, orig_lrn_source_ind, term_lrn, term_ocn, term_lrn_source_ind, send_to_ocn, bda_from_place, bda_from_place_st,
bda_to_place, bda_to_place_st, emi_modules, bda_from_clli, bda_to_clli, bda_to_ocn, bda_csc) FROM stdin;
2004-03-23 21:56:48 [6854] LOG:  server process (PID 6868) was terminated by signal 6
2004-03-23 21:56:48 [6854] LOG:  terminating any other active server processes
2004-03-23 21:56:50 [6869] 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 anot
her 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.
2004-03-23 21:56:50 [6854] LOG:  all server processes terminated; reinitializing
2004-03-23 21:56:51 [6870] LOG:  database system was interrupted at 2004-03-23 21:56:47 EST
2004-03-23 21:56:51 [6870] LOG:  checkpoint record is at 27/90395DE4
2004-03-23 21:56:51 [6870] LOG:  redo record is at 27/90395DE4; undo record is at 0/0; shutdown TRUE
2004-03-23 21:56:51 [6870] LOG:  next transaction ID: 17674; next OID: 119938497
2004-03-23 21:56:51 [6870] LOG:  database system was not properly shut down; automatic recovery in progress
2004-03-23 21:56:51 [6870] LOG:  redo starts at 27/90395E24
2004-03-23 21:56:57 [6870] LOG:  unexpected pageaddr 27/6FF60000 in log file 39, segment 180, offset 16121856
2004-03-23 21:56:57 [6870] LOG:  redo done at 27/B4F5FB98
2004-03-23 21:57:18 [6870] LOG:  database system is ready