-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc Mitchell wrote:
| This is follow-up to a problem first reported on 3/1/04. The problem
| has continued to occur intermittently and recently we experienced the
| first occurrence where the first column of a table was the column where
| the corrupte
On Wed, 17 Mar 2004, Marc Mitchell wrote:
> This is follow-up to a problem first reported on 3/1/04. The problem
> has continued to occur intermittently and recently we experienced the
> first occurrence where the first column of a table was the column where
> the corrupted and thus we could not
"Marc Mitchell" <[EMAIL PROTECTED]> writes:
> This is follow-up to a problem first reported on 3/1/04. The problem
> has continued to occur intermittently and recently we experienced the
> first occurrence where the first column of a table was the column where
> the corrupted and thus we could not
This is follow-up to a problem first reported on 3/1/04. The problem
has continued to occur intermittently and recently we experienced the
first occurrence where the first column of a table was the column where
the corrupted and thus we could not recover it.
Google groups searching have found nume
"Marc Mitchell" <[EMAIL PROTECTED]> writes:
> In each case, by examining the copy table output up to the point where
> it errors out, a single row could be identified that contained corrupted
> char/varchar values but could be queried using primary key or numeric
> lookups. We've been able to work
We are running a highly transaction-intensive application in the
following environment:
Postgres Version 7.3.5 built off the source tree, not RPMs
Operating System: Red Hat Enterprise Linux AS (v 2.1)
Kernel: 2.4.9-e.34smp
Hardware: Dell PE 2600-Dual 2.8 Ghz Xeon w/2GB RAM and Dual 36GB Mirrors
us
