From: Alexandre Leclerc <aleclerc@ipso.ca>
Cc: pgsql-admin@postgresql.org
Subject: Re: Vacuum Full (PG 8.1) - Urgent help needed - Cancel & transaction "liberation"
Date: Fri, 16 Apr 2010 15:29:38 -0400
Message-ID: <4BC8BAA2.1030507@ipso.ca> (raw)
In-Reply-To: <w2pdcc563d11004161220o6a4a4334sf040c37529061052@mail.gmail.com>
References: <4BC8639C.4010202@ipso.ca>
<9048.1271429162@sss.pgh.pa.us>
<4BC8A623.8090201@ipso.ca>
<4BC8638E0200002500030A01@gw.wicourts.gov>
<4BC8B0CE.2010401@ipso.ca>
<w2pdcc563d11004161220o6a4a4334sf040c37529061052@mail.gmail.com>
Le 2010-04-16 15:20, Scott Marlowe a écrit :
> On Fri, Apr 16, 2010 at 12:47 PM, Alexandre Leclerc<aleclerc@ipso.ca> wrote:
>
>> 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.
>>
> You've almost certainly corrupted the data store. This is why you
> should always make a complete file system backup with the postmaster
> stopped before you start doing rescue work.
>
>
Hi Scott and Kevin,
Thank you for these comments. But I'm learning the hard way right now
since all this has already been done. I appreaciate the suggestions of
Kevin on the terminology (since I'm not a native English speaking guy)
and complementing the help. I can assure that it would have been clear
if worded like that, for me at least.
Hopefully, our customer is supposed to have a full file backup from the
evening. So they would have loose only 3 hours of work in that respect.
So the plan is that after the vacuum if the DB is not working well, we
start from the backup, 3 hours before the problem, and we run a VACUUM
using pgAdmin with the normal postmaster during the weekend.
Again, thank you very much for all your time and help. It really is
helping and supportive for me (even if I'm making mistakes).
Best regards,
--
Alexandre Leclerc
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: aleclerc@ipso.ca
Subject: Re: Vacuum Full (PG 8.1) - Urgent help needed - Cancel & transaction "liberation"
In-Reply-To: <4BC8BAA2.1030507@ipso.ca>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox