Thread

1. Copy error

   Marc G. Fournier <scrappy@hub.org> — 1998-05-13T17:59:27Z

   
   ===================================================================
   This message has been sent to a DEAD mailing list, and subsequently 
   reforwarded to the proper one: pgsql-general@postgresql.org
   ===================================================================
   
   
   
   I remember seeing this error on the group about a month ago, but I can't
   recall the answer.
   
   Nightly, we copy 45,000 + lines into a database, last night, the script
   got a "Broken pipe".  The backend reports:
   
   FATAL 1:  my bits moved right off the end of the world!
   
   This script has worked correctly for 6 months.  Postgres version 6.3.1.
   Sparc 20 running Solaris 2.5.1.
   
   Any help?
   
   Thanks,
   
   -Jason E. Neumeier.
   neumeier@bright.net
   
   
   

2. Re: [GENERAL] Copy error

   Bruce Momjian <maillist@candle.pha.pa.us> — 1998-05-13T18:08:48Z

   > I remember seeing this error on the group about a month ago, but I can't
   > recall the answer.
   > 
   > Nightly, we copy 45,000 + lines into a database, last night, the script
   > got a "Broken pipe".  The backend reports:
   > 
   > FATAL 1:  my bits moved right off the end of the world!
   > 
   > This script has worked correctly for 6 months.  Postgres version 6.3.1.
   > Sparc 20 running Solaris 2.5.1.
   > 
   > Any help?
   
   It is from the btree index code, nbtpage.c
   
           if (P_RIGHTMOST(opaque))
               elog(FATAL, "my bits moved right off the end of the world!");
   
   I would drop the index and recreate.  The wording of this error message
   is one of my personal favorites.
   
   
   -- 
   Bruce Momjian                          |  830 Blythe Avenue
   maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
     +  If your life is a hard drive,     |  (610) 353-9879(w)
     +  Christ can be your backup.        |  (610) 853-3000(h)