On Wed, Dec 3, 2008 at 6:25 AM, Gary Schlachter
<[EMAIL PROTECTED]> wrote:
> Straight 7.4. No dot release. I do not doubt this could be a problem
> within the version I am using. However, I am looking for a way to
> correct/recover the database.
Wow. you really need to update to the latest
Gary Schlachter escribió:
>Straight 7.4. No dot release. I do not doubt this could be a
> problem within the version I am using. However, I am looking for a way
> to correct/recover the database.
Update to 7.4.latest, and _then_ try to start the database.
--
Alvaro Herrera
Straight 7.4. No dot release. I do not doubt this could be a
problem within the version I am using. However, I am looking for a way
to correct/recover the database.
Scott Marlowe wrote:
On Tue, Dec 2, 2008 at 2:46 PM, Gary Schlachter
<[EMAIL PROTECTED]> wrote:
I am running postgres 7
On Tue, Dec 2, 2008 at 2:46 PM, Gary Schlachter
<[EMAIL PROTECTED]> wrote:
> I am running postgres 7.4 and solaris 2.9 and I fear I have a corruption.
> The database runs fine for a while and then a command will receive the
> following:
7.4.what? A lot of older 7,4 versions had known data corrup
I am running postgres 7.4 and solaris 2.9 and I fear I have a
corruption. The database runs fine for a while and then a command will
receive the following:
psql: FATAL: xlog flush request 8/20D70938 is not satisfied -- flushed
only to 6/FDBA6540
CONTEXT:writing block 180816 of relation 1
