Postgres Pro
Downloads
Home   >   mailing lists

Thread: Postgres 8.3.7 Server Crash: failed to add item to the right sibling in index

Postgres 8.3.7 Server Crash: failed to add item to the right sibling in index

From
CM J
Date:
Hi,

       I am running Postgres 8.3.7 on Windows 2003 with my java application.Off late, the server crashes with the following trace:

2009-07-01 14:47:07.250 ISTPANIC:  failed to add item to the right sibling in index "mevservices2_ndx"

2009-07-01 14:47:07.250 ISTSTATEMENT:  insert into MEVSERVICES(NSIP,EPTIME,VSVRSVCNAME,VSVRNAME,VSVRSVCENTITYTYPE) values ($1,$2,$3,$4,$5)

 

This application has requested the Runtime to terminate it in an unusual way.

Please contact the application's support team for more information.

 

2009-07-01 14:47:08.609 ISTLOG:  server process (PID 2204) exited with exit code 3

2009-07-01 14:47:08.609 ISTLOG:  terminating any other active server processes

2009-07-01 14:47:08.640 ISTWARNING:  terminating connection because of crash of another server process

2009-07-01 14:47:08.640 ISTDETAIL:  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.

2009-07-01 14:47:08.640 ISTHINT:  In a moment you should be able to reconnect to the database and repeat your command.

2009-07-01 14:47:08.687 ISTWARNING:  terminating connection because of crash of another server process

2009-07-01 14:47:08.687 ISTDETAIL:  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.

2009-07-01 14:47:08.687 ISTHINT:  In a moment you should be able to reconnect to the database and repeat your command.

2009-07-01 14:47:08.828 ISTWARNING:  terminating connection because of crash of another server process

2009-07-01 14:47:08.828 ISTDETAIL:  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.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

   The index is defined on a column of type varchar(100) . Is this is a bug in postgres and is this related to the discussion mentioned in the thread below:

http://www.mail-archive.com/pgsql-hackers@postgresql.org/msg87557.html

 Thanks.


 



Re: Postgres 8.3.7 Server Crash: failed to add item to the right sibling in index

From
Tom Lane
Date:
CM J <postgres.newbie@gmail.com> writes:
>        I am running Postgres 8.3.7 on Windows 2003 with my java
> application.Off late, the server crashes with the following trace:

> *2009-07-01 14:47:07.250 ISTPANIC:  failed to add item to the right sibling
> in index "mevservices2_ndx"*

Sounds like a data corruption problem ... try reindexing that index.

            regards, tom lane

Re: Postgres 8.3.7 Server Crash: failed to add item to the right sibling in index

From
CM J
Date:
>>Sounds like a data corruption problem

After reindexing, the problem seems to go away. Is there any way to determine what caused the data corruption in the first place ??

Thanks.

On Mon, Jul 6, 2009 at 8:29 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
CM J <postgres.newbie@gmail.com> writes:
>        I am running Postgres 8.3.7 on Windows 2003 with my java
> application.Off late, the server crashes with the following trace:

> *2009-07-01 14:47:07.250 ISTPANIC:  failed to add item to the right sibling
> in index "mevservices2_ndx"*

Sounds like a data corruption problem ... try reindexing that index.

                       regards, tom lane