Re: Cannot start Postgres- FATAL: invalid cache id: 19 - Mailing list pgsql-general

From Jolles, Peter M (GE Energy)
Subject Re: Cannot start Postgres- FATAL: invalid cache id: 19
Date
Msg-id E66B1BA008C7374390C6AE9EF01E584A03B5D219@ALPMLVEM08.e2k.ad.ge.com
Whole thread Raw
In response to Re: Cannot start Postgres- FATAL: invalid cache id: 19  (Vick Khera <vivek@khera.org>)
Responses Re: Cannot start Postgres- FATAL: invalid cache id: 19  (Vick Khera <vivek@khera.org>)
Re: Cannot start Postgres- FATAL: invalid cache id: 19  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Cannot start Postgres- FATAL: invalid cache id: 19  (Adrian Klaver <adrian.klaver@gmail.com>)
List pgsql-general
On Wednesday, December 01, 2010 1:59 PM Vick Khera wrote:
> the original hint said to "use a standalone backend".
>
> If you go to http://www.postgresql.org/docs/9.0/interactive/routine-
> vacuuming.html
> section 23.1.4 it will describe exactly what just happened to you and
how to
> recover.

I apologize for the seeming dumb questions, but I have tried to start
the database using the following command:

postgres --single -D "d:/database" mydatabase

That gets me a new line in my command prompt window and nothing else.
Postgres 8.4 at least throws a warning if I am not logged in as an under
privileged user, but 9.0 gives nothing, no log file entries or other
error message that indicates it is trying and why it is failing. Using
the -r command didn't produce a log file.

Trying to run the vacuumdb.exe command fails because the database isn't
running. Using pg_ctl I can get a response, but it gives the same
startup error as originally mentioned. I must be missing something, but
I don't see what it is.

pgsql-general by date:

Previous
From: "Andrus"
Date:
Subject: Re: How to find correct locale name for CREATE DATABASE
Next
From: "James B. Byrne"
Date:
Subject: PG_ERROR 42501 permissions error