Hey..
First .. I´m sorry for my english! ..
Well, I have a problem with Postgres 7.4.
It´s very very crazy, this error!...
I have a problem with a command of insert. And this problem is resulting in
a error Panic! . (I will put the error below).
The more problem is that I have two insert equals, only change one
information, and a the result is OK, and the other is not OK.
Inserts:
OK:
insert into provisioning.t_usuario (
cd_usuario,msisdn,cd_operadora,tp_plano,st_usuario,ds_modelo ) values
(nextval('provisioning.s01_usuario'),'555584016386','61','PRE','0','' )
NOK
insert into provisioning.t_usuario (
cd_usuario,msisdn,cd_operadora,tp_plano,st_usuario,ds_modelo ) values
(nextval('provisioning.s01_usuario'),'556184000828','61','PRE','0','' )
In the secund, happen this error in log of postgres:
Jan 29 11:40:59 mw-db2 postgres[31921]: [6-1] PANIC: right sibling's
left-link doesn't match
Jan 29 11:40:59 mw-db2 postgres[31921]: [6-2] STATEMENT: insert into
provisioning.t_usuario (
cd_usuario,msisdn,cd_operadora,tp_plano,st_usuario,ds_modelo ) values (
Jan 29 11:40:59 mw-db2 postgres[31921]: [6-3] nextval('
provisioning.s01_usuario'),'556184000828','61','PRE','0','' )
Jan 29 11:40:59 mw-db2 postgres[6100]: [5-1] LOG: server process (PID
31921) was terminated by signal 6
Jan 29 11:40:59 mw-db2 postgres[6100]: [6-1] LOG: terminating any other
active server processes
Jan 29 11:40:59 mw-db2 postgres[5395]: [5-1] WARNING: terminating
connection because of crash of another server process
Jan 29 11:40:59 mw-db2 postgres[32631]: [7-1] WARNING: of another server
process
Jan 29 11:40:59 mw-db2 postgres[651]: [5-1] WARNING: terminating connection
because of crash of another serterminating connection because of crash ver
process
Jan 29 11:40:59 mw-db2 postgres[5395]: [5-2] DETAIL: The postmaster has
commanded this server process to roll back the current transaction and exit,
because another server
Jan 29 11:40:59 mw-db2 postgres[32631]: [7-2] DETAIL: The postmaster has
commanded this server process to roll back the current transaction and exit,
because another server
Jan 29 11:40:59 mw-db2 postgres[651]: [5-2] DETAIL: The postmaster has
commanded this server process to roll back the current transaction and exit,
because another server
Jan 29 11:40:59 mw-db2 postgres[5395]: [5-3] process exited abnormally and
possibly corrupted shared memory.
Jan 29 11:40:59 mw-db2 postgres[32631]: [7-3] process exited abnormally and
possibly corrupted shared memory.
Jan 29 11:40:59 mw-db2 postgres[651]: [5-3] process exited abnormally and
possibly corrupted shared memory.
Jan 29 11:40:59 mw-db2 postgres[5395]: [5-4] HINT: In a moment you should
be able to reconnect to the database and repeat your command.
Jan 29 11:40:59 mw-db2 postgres[32631]: [7-4] HINT: In a moment you should
be able to reconnect to the database and repeat your command.
Jan 29 11:40:59 mw-db2 postgres[4537]: [5-1] WARNING: terminating
connection because of crash of another server process
Jan 29 11:40:59 mw-db2 postgres[32632]: [7-1] WARNING: terminating
connection because of crash of another server process
Jan 29 11:40:59 mw-db2 postgres[32506]: [5-1] WARNING: terminating
connection because of crash of another server process
Jan 29 11:40:59 mw-db2 postgres[32384]: [5-1] WARNING: terminating
connection because of crash of another server process
Jan 29 11:40:59 mw-db2 postgres[32509]: [5-1] WARNING: terminating
connection because of crash of another server process
Jan 29 11:40:59 mw-db2 postgres[32508]: [5-1] WARNING: terminating
connection because of crash of another server process
Jan 29 11:40:59 mw-db2 postgres[31925]: [5-1] WARNING: terminating
connection because of crash of another server process
Jan 29 11:40:59 mw-db2 postgres[31924]: [5-1] WARNING: terminating
connection because of crash of another server process
Jan 29 11:40:59 mw-db2 postgres[32507]: [5-1] WARNING: terminating
connection because of crash of another server process
Jan 29 11:40:59 mw-db2 postgres[32383]: [5-1] WARNING: terminating
connection because of crash of another server process
Jan 29 11:40:59 mw-db2 postgres[31920]: [5-1] WARNING: terminating
connection because of crash of another server process
Jan 29 11:40:59 mw-db2 postgres[31799]: [5-1] WARNING: terminating
connection because of crash of another server process
Jan 29 11:40:59 mw-db2 postgres[651]: [5-4] HINT: In a moment you should be
able to reconnect to the database and repeat your command.
Jan 29 11:40:59 mw-db2 postgres[4537]: [5-2] DETAIL: The postmaster has
commanded this server process to roll back the current transaction and exit,
because another server
Jan 29 11:40:59 mw-db2 postgres[32632]: [7-2] DETAIL: The postmaster has
commanded this server process to roll back the current transaction and exit,
because another server
Jan 29 11:40:59 mw-db2 postgres[32506]: [5-2] DETAIL: The postmaster has
commanded this server process to roll back the current transaction and exit,
because another server
Jan 29 11:40:59 mw-db2 postgres[32384]: [5-2] DETAIL: The postmaster has
commanded this server process to roll back the current transaction and exit,
because another server
Jan 29 11:40:59 mw-db2 postgres[32509]: [5-2] DETAIL: The postmaster has
commanded this server process to roll back the current transaction and exit,
because another server
Jan 29 11:40:59 mw-db2 postgres[32508]: [5-2] DETAIL: The postmaster has
commanded this server process to roll back the current transaction and exit,
because another server
Jan 29 11:40:59 mw-db2 postgres[31925]: [5-2] DETAIL: The postmaster has
commanded this server process to roll back the current transaction and exit,
because another server
Jan 29 11:40:59 mw-db2 postgres[31924]: [5-2] DETAIL: The postmaster has
commanded this server process to roll back the current transaction and exit,
because another server
Jan 29 11:40:59 mw-db2 postgres[32507]: [5-2] DETAIL: The postmaster has
commanded this server process to roll back the current transaction and exit,
because another server
Jan 29 11:40:59 mw-db2 postgres[32383]: [5-2] DETAIL: The postmaster has
commanded this server process to roll back the current transaction and exit,
because another server
Jan 29 11:40:59 mw-db2 postgres[31920]: [5-2] DETAIL: The postmaster has
commanded this server process to roll back the current transaction and exit,
because another server
Jan 29 11:40:59 mw-db2 postgres[31799]: [5-2] DETAIL: The postmaster has
commanded this server process to roll back the current transaction and exit,
because another server
Jan 29 11:40:59 mw-db2 postgres[4537]: [5-3] process exited abnormally and
possibly corrupted shared memory.
Jan 29 11:40:59 mw-db2 postgres[32632]: [7-3] process exited abnormally and
possibly corrupted shared memory.
Jan 29 11:40:59 mw-db2 postgres[32506]: [5-3] process exited abnormally and
possibly corrupted shared memory.
Jan 29 11:40:59 mw-db2 postgres[32384]: [5-3] process exited abnormally and
possibly corrupted shared memory.
Jan 29 11:40:59 mw-db2 postgres[32509]: [5-3] process exited abnormally and
possibly corrupted shared memory.
Jan 29 11:40:59 mw-db2 postgres[32508]: [5-3] process exited abnormally and
possibly corrupted shared memory.
Jan 29 11:40:59 mw-db2 postgres[31925]: [5-3] process exited abnormally and
possibly corrupted shared memory.
Jan 29 11:40:59 mw-db2 postgres[31924]: [5-3] process exited abnormally and
possibly corrupted shared memory.
Jan 29 11:40:59 mw-db2 postgres[32507]: [5-3] process exited abnormally and
possibly corrupted shared memory.
Jan 29 11:40:59 mw-db2 postgres[32383]: [5-3] process exited abnormally and
possibly corrupted shared memory.
Jan 29 11:40:59 mw-db2 postgres[31920]: [5-3] process exited abnormally and
possibly corrupted shared memory.
Jan 29 11:40:59 mw-db2 postgres[31799]: [5-3] process exited abnormally and
possibly corrupted shared memory.
Jan 29 11:40:59 mw-db2 postgres[4537]: [5-4] HINT: In a moment you should
be able to reconnect to the database and repeat your command.
Jan 29 11:40:59 mw-db2 postgres[32632]: [7-4] HINT: In a moment you should
be able to reconnect to the database and repeat your command.
Jan 29 11:40:59 mw-db2 postgres[32506]: [5-4] HINT: In a moment you should
be able to reconnect to the database and repeat your command.
Jan 29 11:40:59 mw-db2 postgres[32384]: [5-4] HINT: In a moment you should
be able to reconnect to the database and repeat your command.
Jan 29 11:40:59 mw-db2 postgres[32509]: [5-4] HINT: In a moment you should
be able to reconnect to the database and repeat your command.
Jan 29 11:40:59 mw-db2 postgres[32508]: [5-4] HINT: In a moment you should
be able to reconnect to the database and repeat your command.
Jan 29 11:40:59 mw-db2 postgres[31925]: [5-4] HINT: In a moment you should
be able to reconnect to the database and repeat your command.
Jan 29 11:40:59 mw-db2 postgres[31924]: [5-4] HINT: In a moment you should
be able to reconnect to the database and repeat your command.
Jan 29 11:40:59 mw-db2 postgres[32507]: [5-4] HINT: In a moment you should
be able to reconnect to the database and repeat your command.
Jan 29 11:40:59 mw-db2 postgres[32383]: [5-4] HINT: In a moment you should
be able to reconnect to the database and repeat your command.
Jan 29 11:40:59 mw-db2 postgres[31920]: [5-4] HINT: In a moment you should
be able to reconnect to the database and repeat your command.
Jan 29 11:40:59 mw-db2 postgres[31799]: [5-4] HINT: In a moment you should
be able to reconnect to the database and repeat your command.
Jan 29 11:40:59 mw-db2 postgres[6100]: [7-1] LOG: all server processes
terminated; reinitializing
Jan 29 11:40:59 mw-db2 postgres[6706]: [8-1] LOG: database system was
interrupted at 2007-01-29 11:38:16 BRDT
Jan 29 11:40:59 mw-db2 postgres[6706]: [9-1] LOG: checkpoint record is at
30/A0633008
Jan 29 11:40:59 mw-db2 postgres[6706]: [10-1] LOG: redo record is at
30/A0633008; undo record is at 0/0; shutdown FALSE
Jan 29 11:40:59 mw-db2 postgres[6706]: [11-1] LOG: next transaction ID:
590689926; next OID: 49672068
Jan 29 11:40:59 mw-db2 postgres[6706]: [12-1] LOG: database system was not
properly shut down; automatic recovery in progress
Jan 29 11:40:59 mw-db2 postgres[6706]: [13-1] LOG: redo starts at
30/A0633048
Jan 29 11:40:59 mw-db2 postgres[6706]: [14-1] LOG: record with zero length
at 30/A06BB3D8
Jan 29 11:40:59 mw-db2 postgres[6706]: [15-1] LOG: redo done at 30/A06BB3B4
Jan 29 11:41:01 mw-db2 postgres[6706]: [16-1] LOG: database system is ready
both are only examples, bacause is having many error like these!
I thank the help a lot.
--
ZappA
Msn: [EMAIL PROTECTED]
