Search Postgresql Archives

Re: could not read block... how could I identify/fix

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Naoko Reeves <naokoreeves@xxxxxxxxx>
Subject: Re: could not read block... how could I identify/fix
From: Vick Khera <vivek@xxxxxxxxx>
Date: Thu, 29 Mar 2012 10:10:32 -0400
Cc: pgsql-general@xxxxxxxxxxxxxx
In-reply-to: <CAGoos15NYOczh_WLN22io3tpnSekTiY=WdGsayDbYQ6dR3p2-w@mail.gmail.com>

On Wed, Mar 28, 2012 at 6:31 PM, Naoko Reeves <naokoreeves@xxxxxxxxx> wrote:
> Version: "PostgreSQL 8.4.6 on

Oh, and also upgrade to 8.4.11 to ensure you do not have any known
data loss bugs.

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- could not read block... how could I identify/fix
  - From: Naoko Reeves

Prev by Date: More PG Log
Next by Date: Re: More PG Log
Previous by thread: Re: could not read block... how could I identify/fix
Next by thread: scripted 'pg_ctl start' hangs and never finishes, goes <defunct>
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux