Hi,
thanks alot for your answers.
Yesterday I have updated the kernel. After a reboot, the ECC-Kernel error still appears. Then I've cleaned
the RAM-Slots with nose-paper :), rebooted the machine, and the error was away! Unbelievable, the error
was before on both the machines.
Yesterday night, i've switched my Slony-replication and the IP address. Right now, thanks to god, I'm on a
safe side. :)
Now i will clean the old production machine :) and putting it back to the replication. :)
Over again, thanks very much, I like PostgreSQL and the Community, it's a very very good project :)!
Regards,
Martin
-----Ursprüngliche Nachricht-----
Von: Tom Lane <tgl@sss.pgh.pa.us>
Gesendet: 08.08.07 18:36:09
An: "Nick Fankhauser" <nickf@doxpop.com>
CC: pgsql-admin@postgresql.org
Betreff: Re: [ADMIN] Specific questions about wraparound and vacuum
"Nick Fankhauser" <nickf@doxpop.com> writes:
> 1) Do we need to do a *full* vacuum or just a "lazy" vacuum to take care of
> the xid wraparound issues?
Lazy is sufficient --- as long as it's database-wide including the
system catalogs (which means a superuser has to do it).
> Or... is it the case that by one billion, the docs really mean 2^30
> (1073741824) ?
2^30. You appear to have executed a bit under 600000 transactions since
vacuuming, so if that's three hours then you've got about 5000 hours
until wraparound.
> 4) The documentation implies that I need to vacuum *every* database, even if
> I'm not using them all, so I vacuumed template1, but can't connect to
> template0. Do I really need to vacuum databases where no transactions are
> occurring? If so, how to I deal with template0?
You don't need to touch frozen databases. This was discussed yesterday ...
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
_______________________________________________________________________
Jetzt neu! Schützen Sie Ihren PC mit McAfee und WEB.DE. 3 Monate
kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=022220
