Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: corruption since 7.4.13 update ?
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: FM <dist-list(at)LEXUM(dot)UMontreal(dot)CA>
- Cc: Mailing List Postgres-Admin <pgsql-admin(at)postgresql(dot)org>
- Subject: Re: corruption since 7.4.13 update ?
- Date: Thu, 13 Jul 2006 20:40:10 -0400
FM <dist-list(at)LEXUM(dot)UMontreal(dot)CA> writes: > I'e got a very strange (scary) problem. > ERROR: could not read block 81235 of relation "pg_largeobject": > Input/output error This one is very strongly indicative of a disk hardware problem. The others look like they could be consequences of catalog corruption ensuing from a flaky disk. If I were you I'd run some hardware diagnostics. Also see if you can pg_dump ... regards, tom lane
- References:
- corruption since 7.4.13 update ?
- From: FM
- corruption since 7.4.13 update ?
- Prev by Date: Determining object name from filenode
- Next by Date: Table size growing for no reason
- Previous by thread: corruption since 7.4.13 update ?
- Next by thread: solaris and postgresql and locale
- Indexes: