On Wednesday 01 December 2010 1:15:45 pm Jolles, Peter M (GE Energy) wrote:
> 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
> > secti
"Jolles, Peter M (GE Energy)" writes:
> 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.
Hmm ... try it with "
On Wed, Dec 1, 2010 at 4:15 PM, Jolles, Peter M (GE Energy)
wrote:
> 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 nothi
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 a
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.
On Wed, Dec 1, 2010 at 1:58 PM, Jolles, Peter M (GE Energy)
wrote:
> Is
On Wednesday, December 01, 2010 1:27 PM Vick Khera wrote:
> Just how big is the table and how many transactions per second do you
push
> through it? Perhaps your I/O bandwidth is just insufficient for your
load
> level.
>
The entire database is about 700 GB. In the database I've got
approximatel
On Wed, Dec 1, 2010 at 11:23 AM, Jolles, Peter M (GE Energy)
wrote:
> EST WARNING: database "fps_data" must be vacuumed within 1100
> transactions
>
> I know now that I'm going to have to slow down the transaction rate in order
> to let the autovacuum keep up, but at this point I am just tr
On Wednesday, December 01, 2010 9:58 AM Vick Khera wrote:
> On Wed, Dec 1, 2010 at 9:20 AM, Jolles, Peter M (GE Energy) wrote:
> > 2010-11-29 12:39:17 EST HINT: Stop the postmaster and use a
> > standalone backend to vacuum that database.
>
> so did you do what the HINT told you to do? does it
Vick Khera writes:
> On Wed, Dec 1, 2010 at 9:20 AM, Jolles, Peter M (GE Energy)
> wrote:
>> 2010-11-29 12:39:17 EST HINT: Stop the postmaster and use a standalone
>> backend to vacuum that database.
> so did you do what the HINT told you to do? does it still not startup?
This is the second r
On Wed, Dec 1, 2010 at 9:20 AM, Jolles, Peter M (GE Energy)
wrote:
> 2010-11-29 12:39:17 EST HINT: Stop the postmaster and use a standalone
> backend to vacuum that database.
so did you do what the HINT told you to do? does it still not startup?
>
> I had multiple auto-vacuum instances running
I am having problems starting up Postgres and am getting the following
error:
2010-12-01 08:36:42 EST LOG: database system was shut down at
2010-11-29 17:38:17 EST
2010-12-01 08:36:42 EST FATAL: invalid cache id: 19
2010-12-01 08:36:43 EST FATAL: the database system is starting up
2010-12-01 08
11 matches
Mail list logo
