BUG #2255: Broken a database... Completly destroyed...

The following bug has been logged online:

Bug reference: 2255
Logged by: Estagus
Email address: wizard580(at)gmail(dot)com
PostgreSQL version: 8.1.2
Operating system: Debian AMD64/em64t sarge 3.1 sid unstable
Description: Broken a database... Completly destroyed...
Details:

After a month of a fine work I noticed a constant grow of a my database
files size... I've make a server restart... Server stopped but not
started... Seems it destroyed all my data... (thanx god I have croned backup
10 min before...)

My log here:
-----------------------------------------------------
LOG: received fast shutdown request
LOG: aborting any active transactions
FATAL: terminating connection due to administrator command
CONTEXT: SQL statement "CREATE TEMP TABLE temp_tarifsdetails AS SELECT *
FROM tarifsdetails WHERE tarif_id = $1 ORDE
R BY tar_order"
PL/pgSQL function "price_traffic" line 69 at SQL statement
PL/pgSQL function "calc_traffic_price" line 50 at assignment
SQL statement "INSERT INTO
ulog_lastmin(time,iface_in,iface_out,protocol,src,sport,dst,dport,size,host_
prefix,u
ser_id_in,user_id_out) VALUES( $1 , $2 , $3 , $4 , $5 , $6 , $7 , $8 ,
$9 , $10 , $11 , $12 )"
PL/pgSQL function "ulog_add" line 65 at SQL statement
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
FATAL: the database system is shutting down
LOG: received immediate shutdown request
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 anothe
r 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.
LOG: database system was interrupted at 2006-02-13 12:22:25 VLAT
LOG: checkpoint record is at A0/40267530
LOG: redo record is at A0/40267530; undo record is at 0/0; shutdown FALSE
LOG: next transaction ID: 61358923; next OID: 135917978
LOG: next MultiXactId: 4; next MultiXactOffset: 7
LOG: database system was not properly shut down; automatic recovery in
progress
LOG: redo starts at A0/40267580
LOG: incomplete startup packet
FATAL: the database system is starting up
FATAL: the database system is starting up
FATAL: the database system is starting up
FATAL: the database system is starting up
PANIC: heap_insert_redo: uninitialized page
LOG: startup process (PID 15500) was terminated by signal 6
LOG: aborting startup due to startup process failure
LOG: database system was interrupted while in recovery at 2006-02-13
12:24:36 VLAT
HINT: This probably means that some data is corrupted and you will have to
use the last backup for recovery.
LOG: checkpoint record is at A0/40267530
LOG: redo record is at A0/40267530; undo record is at 0/0; shutdown FALSE
LOG: next transaction ID: 61358923; next OID: 135917978
LOG: next MultiXactId: 4; next MultiXactOffset: 7
LOG: database system was not properly shut down; automatic recovery in
progress
LOG: redo starts at A0/40267580
PANIC: heap_insert_redo: uninitialized page
LOG: startup process (PID 15551) was terminated by signal 6
LOG: aborting startup due to startup process failure
LOG: database system was interrupted at 2006-01-01 22:15:19 VLAT

and so on.....