On Tue, 2011-05-03 at 01:14 -0400, Tom Lane wrote:
> Craig Ringer writes:
> > This message is very weird: "could not read from file "pg_clog/02CD" at
> > offset 73728: Success".
>
> Probably indicates an attempted read from beyond EOF. The main
> relation-access code paths have been fixed to giv
Craig Ringer writes:
> This message is very weird: "could not read from file "pg_clog/02CD" at
> offset 73728: Success".
Probably indicates an attempted read from beyond EOF. The main
relation-access code paths have been fixed to give a more intelligible
error message about that case, but it doe
On 02/05/11 03:32, Iztok Stotl wrote:
> My database crashed and server won't start ...
>
> --
> LOG: database system was interrupted while in recovery at 2011-05-01
> 19:31:37 CEST
> HINT: This probably means that some data is corrupted and you
My database crashed and server won't start ...
--
LOG: database system was interrupted while in recovery at 2011-05-01
19:31:37 CEST
HINT: This probably means that some data is corrupted and you will have
to use the last backup for recovery.
LO
ovember 30, 2000 2:24 PM
To: Hancock, David (DHANCOCK)
Cc: '[EMAIL PROTECTED]'
Subject: Re: [GENERAL] Help with Database Recovery
"Hancock, David (DHANCOCK)" <[EMAIL PROTECTED]> writes:
> Sorry I didn't give more detail. OS is Linux 2.2 kernel, PostgreSQL i
"Hancock, David (DHANCOCK)" <[EMAIL PROTECTED]> writes:
> Sorry I didn't give more detail. OS is Linux 2.2 kernel, PostgreSQL is
> 6.5.3. The problem is that I copied the .../base/* directories elsewhere in
> preparation for making base a symlink to a different filesystem with more
> space. I t
