Hi Tom,
We recreated the index and that fixed it last week. We also had similar
failure few days back on a table but fortunately we had the luxury of
recreating it as the data was not so important, so we survived.
Yesterday we upgraded our postgres databases to 8.0.15 as suggested and
again we g
"Bhella Paramjeet-PFCW67" <[EMAIL PROTECTED]> writes:
> Error in the database vacuum log.
> INFO: vacuuming "public.securityevent"
> WARNING: relation "securityevent" TID 21/3: OID is invalid
That smells like a data corruption problem ...
> vacuumdb: vacuuming of database "ectest" failed: ERROR
Hi Eric,
No database is not sitting on NFS storage. We are using emc storage and
the file system is fibre attached to storage.
In last few days we have had lots of errors on the database. Last night
while taking a pg_dump we got invalid memory alloc request error "ecdemo
2008-04-25 00:40:31 CDTFA
> -Original Message-
> From: Bhella Paramjeet-PFCW67 [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 24, 2008 1:13 PM
> To: Tom Lane
> Cc: pgsql-admin@postgresql.org; Subbiah Stalin-XCGF84
> Subject: Re: Vacuumdb error - corruption
>
>
> According to our sysadmin there are no bad disk
On Fri, Apr 25, 2008 at 06:03:12PM -0400, Bhella Paramjeet-PFCW67 wrote:
> No database is not sitting on NFS storage. We are using emc storage and
> the file system is fibre attached to storage.
What's the filesystem? Are you sure you don't have any bad memory in
the box? I'm suspicious of the
