Le 2010-04-16 14:18, Kevin Grittner a écrit :
Alexandre Leclerc<aleclerc@xxxxxxx> 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
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
