Re: Corrupt Table

Here is a follow up.  I did a hex/ascii dump of the 3 bad tuples.  In the
dump I could pick out an email address.  This is an indexed field.  I did a
select on each of them in the live database.  The 1st and 3rd were not
found.  The second worked ok if I only selected the customer id (an int4 and
the first field in the record).  The custid reported seems to be nonsense.
The backend crashed if I selected the whole record.