Re: Vacuum Full (PG 8.1) - Urgent help needed - Cancel & transaction "liberation"

Hi again,

I also want to mention that maybe I'm not doing it properly.

I started "postgres.exe" and it is inside that "session", "backend>"
prompt, that I did run the VACUUM command. Is it that way or should I
use psql to connect to anything "postgres.exe" would have "done" (like
listening to a port?).

(And by the way, what is the command to quit the backend? I'm doing
Ctrl+C but the DB does not like that...)

Best regards,
Alexandre Leclerc

Le 2010-04-16 10:46, Tom Lane a écrit :
> Alexandre Leclerc<aleclerc(at)ipso(dot)ca> writes:
>
>> *Background:*
>> - PostgreSQL 8.1 on Windows Server
>> - The customer has disabled regular VACUUM jobs for backup to be taken,
>> a year or two ago.
>> - They didn't told us (as far as I can remember).
>> - Wednesday morning at 10:55:50: database is shut down to avoid
>> wraparound data loss in database *db*
>>
>
>> *What has been done:*
>> - The message requested a VACUUM FULL so we stopped the postmaster and
>> started postgres.exe to launch a VACUUM FULL.
>>
> You misread it. You do NOT need a VACUUM FULL here, you should just run
> a plain VACUUM (across the whole database, ie not one per table). It
> will take a lot less time.
>
> After you get out of this, you really need to do something about
> upgrading from 8.1, or else moving the server off Windows. 8.1 on
> Windows is unsupported and is full of known problems for that platform.
>
> regards, tom lane
>
>

--
Alexandre Leclerc