Re: ERROR: Index pg_toast_8443892_index is not a btree

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, strk <strk(at)keybit(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: ERROR: Index pg_toast_8443892_index is not a btree
Date: 2003-12-10 01:19:39
Message-ID: 3FD674AB.5070707@Yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Christopher Kings-Lynne wrote:

>> I couldn't agree more. Look at this very instance. He now found the
>> right reindex command and the corrupted file is gone. We don't have the
>> slightest clue what happened to that file. Was it truncated? Did some
>> other process scribble around in the shared memory? How do you tell now?
>
> The end user just could not care less. They want their machine running
> again as soon as is humanly possible without going through a back and
> forth process of subscribing to some lists they don't care about, etc.

I know, that's (unfortunately) true. Although it's not very farsighted
because better bug reports usually lead to better software in the next
release.

Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Cramer 2003-12-10 02:00:52 Re: PostgreSQL port to pure Java?
Previous Message markw 2003-12-10 00:27:06 DBT-2 running against PostgreSQL and LVM2