Re: postgres 6.2 vacuum - Mailing list pgsql-admin

From Hornyak Laszlo
Subject Re: postgres 6.2 vacuum
Date
Msg-id Pine.LNX.4.21.0309240953550.19598-100000@tiger.tigrasoft.hu
Whole thread Raw
In response to Re: postgres 6.2 vacuum  ("scott.marlowe" <scott.marlowe@ihs.com>)
List pgsql-admin
Yes, at the end we did the port at night, and in the morning the system
started without any problem. Some of the dumps from pg 6.2 was not realy
acceptable by 7.3, but it was easy to fix.

Thank you for your help!

Laszlo Hornyak

On Tue, 23 Sep 2003, scott.marlowe wrote:

> On Mon, 22 Sep 2003, Hornyak Laszlo wrote:
>
> > Hi all!
> >
> > We have a database on postgreSQL 6.2 and it is extremely slow, so we
> > started vacuum on it. I know it locks the tables, so clients can not use
> > it until the process is finished, but it is extremely slow on a 1.800.000
> > record table and we don't know how to make it faster. Can anybody help me?
> >
> > It seems it is writing an index file, but it grows very slowly.
> >
> > I know we should use 7.3 at least, we are working on it, but we need to
> > survive this day with 6.2 :(
>
> In all honesty, it'd probably be faster to convert than to wait for that
> vacuum to finish.
>
> seriously.
>
> 6.2 is like the model A of Postgresql versions.
>


pgsql-admin by date:

Previous
From: maillist
Date:
Subject: Re: Fatal error: Allowed memory size of 8388608 bytes exhausted
Next
From: Geoffrey
Date:
Subject: Re: export data from excel to postges