Re: Re: COPY error: pqReadData() -- backend closed the channel unexpectedly

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Lee Joramo <lee(dot)list(at)joramo(dot)com>
Cc: rob <rob(at)cabrion(dot)com>, postgre general list <pgsql-general(at)postgresql(dot)org>
Subject: Re: Re: COPY error: pqReadData() -- backend closed the channel unexpectedly
Date: 2001-01-09 23:50:09
Message-ID: 7740.979084209@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Lee Joramo <lee(dot)list(at)joramo(dot)com> writes:
> And the solution is:
> DELETE INDEX classifieds_adcopy
> By deleteing the index, everything started to work correctly. Even after
> recreating the index, everyting worked after multiple tests.

So that index had gotten corrupted at some time in the past, and just
emptying and refilling the table didn't fix it. Doesn't surprise me
a whole lot. (I had assumed you were destroying and rebuilding the
whole database, else I'd have suggested this sooner...)

It's possible that the index corruption was triggered by having inserted
an overlength adcopy value at some time in the past. Or maybe it's just
a garden-variety bug; 6.5 has its share of 'em. I do urge you to update
to 7.0.3 as soon as possible. (BTW, there are LinuxPPC RPMs of 7.0.3
available from our FTP server, so if it's having to compile from source
that's scaring you, you don't need to.)

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jeff Eckermann 2001-01-10 00:25:38 "Cluster" means "tangle" for me
Previous Message Stephan Szabo 2001-01-09 23:02:18 Re: drop table and references