Message-ID: <4BC8B0CE.2010401@ipso.ca>
Date: Fri, 16 Apr 2010 14:47:42 -0400
From: Alexandre Leclerc <aleclerc@ipso.ca>
Organization: Ipso Technologies
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr;
	rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: pgsql-admin@postgresql.org
Subject: Re: Vacuum Full (PG 8.1) - Urgent help needed - Cancel	 &
	transaction "liberation"
References: <4BC8639C.4010202@ipso.ca> <9048.1271429162@sss.pgh.pa.us>
	<4BC8A623.8090201@ipso.ca>
	<4BC8638E0200002500030A01@gw.wicourts.gov>
In-Reply-To: <4BC8638E0200002500030A01@gw.wicourts.gov>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Le 2010-04-16 14:18, Kevin Grittner a écrit :
> Alexandre Leclerc<aleclerc@ipso.ca>  wrote:
>
>    
>> At some point I got:
>> ERROR: xlog flush request AC/FBEEF148 is not satisfied --- flushed
>> only to AC/FB9224A8
>> CONTEXT: writing block 0 of relation 1664/0/1214
>> WARNING: could not writing block 0 of 1664/0/1214
>> DETAIL: Multiple failures --- write error may be permanent.
>>      
>
> You're not running out of disk space where that writes, are you?
>    

There is 32 GB free.

>
>    
>> It looks like the vacuum command does not want to be execute. The
>> other VACUUM is still progressing on the main database in another
>> postgres.exe shell.
>>      
>
> Wait -- are you saying you're running two postgres instances against
> the same data directory at the same time?  (I sure hope not.)
>    

I did. :( Shame on me. I just realised while reading doc on postgres 
that it is not made for that but only for a single instance at the time. 
I hope I did not break anything.

>> (If it's the only solution, is it possible to migration from one
>> DB directly to the other under windows... I don't know about the |
>> command under "windows cmd".)
>>      
>
> Yeah, that should work as long as you have the disk space for both
> copies.
>
> -Kevin
>    

Thank you Kevin for you time, it's most appreciated.

Right now I'll leave the standard VACUUM complete it's job. Then I'll 
vacuum the postgres and template1 DB if required.

Best regards,

-- 
Alexandre Leclerc