Re: postgres 6.2 vacuum

From: Hornyak Laszlo <kocka(at)tigrasoft(dot)hu>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: postgres 6.2 vacuum
Date: 2003-09-24 08:00:12
Message-ID: Pine.LNX.4.21.0309240953550.19598-100000@tiger.tigrasoft.hu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers


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.
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Arjen van der Meijden 2003-09-24 09:52:36 Re: [GENERAL] Fatal error: Allowed memory size of 8388608
Previous Message maillist 2003-09-24 06:52:59 Re: Fatal error: Allowed memory size of 8388608 bytes exhausted

Browse pgsql-hackers by date

  From Date Subject
Next Message Manfred Koizar 2003-09-24 09:14:19 Re: osdl-dbt3 run results - puzzled by the execution
Previous Message Michael Meskes 2003-09-24 07:51:13 Re: ecpg build on AIX 4.2.1