pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Anagha Joshi <ajoshi@nulinkinc.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Seqno. is not btree?
Date: Mon, 30 Jun 2003 10:26:55 -0400
Message-ID: <4536.1056983215@sss.pgh.pa.us> (raw)
In-Reply-To: <FF851C7EEB75954F9BCFB5CA117AB1EC092845@delta.nulinkinc.com>
References: <FF851C7EEB75954F9BCFB5CA117AB1EC092845@delta.nulinkinc.com>

"Anagha Joshi" <ajoshi@nulinkinc.com> writes:
> After as many as 2412081 records are inserted,  I shutdown my server.

> Next day,I tried the following:
> test=3D# select count(*) from vchar;
>  count
> -------
>   2568
> (1 row)
> test=3D# insert into vchar (col_var) values ('VV');
> ERROR:  Index vchar_seqno_key is not a btree

It sounds to me like you've got serious disk problems --- losing a
couple hundred thousand rows is not normal :-(.  The index complaint
also suggests on-disk corruption --- it means that the btree version
information that's stored in the first page of a btree index wasn't
right.

How exactly did you "shut down the server"?  Have you noticed any other
evidence of disk problems, outside Postgres?

			regards, tom lane



view thread (2+ messages)

Message-ID: <4536.1056983215@sss.pgh.pa.us>
Permalink:  ../4536.1056983215@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/4536.1056983215@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, ajoshi@nulinkinc.com
  Subject: Re: Seqno. is not btree?
  In-Reply-To: <4536.1056983215@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox