On 05/22/2013 08:49 AM, RDNikeAir wrote:
> I have a database that is on a RAID5 machine that is almost out of memory
> (277GB of 330GB used). I have deleted some data and run the VACUUM FULL
> command, but after a few hours gave me the error message "Server closed the
> connection unexpectedly. Th
RDNikeAir wrote:
> Interestingly enough all the pgsql.log.* files are blank (0 KB) and the last
> message i have in messages.* is from a few days ago. So there are no recent
> entries that i can look at.
Well, it is clear then that the first thing you need to do is fix your
logging.
--
Álvaro H
Interestingly enough all the pgsql.log.* files are blank (0 KB) and the last
message i have in messages.* is from a few days ago. So there are no recent
entries that i can look at.
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/VACUUM-FULL-freezes-tp5756477p5756484.ht
On Wed, May 22, 2013 at 8:49 AM, RDNikeAir wrote:
> I have a database that is on a RAID5 machine that is almost out of memory
> (277GB of 330GB used). I have deleted some data and run the VACUUM FULL
> command, but after a few hours gave me the error message "Server closed the
> connection unexpe
I have a database that is on a RAID5 machine that is almost out of memory
(277GB of 330GB used). I have deleted some data and run the VACUUM FULL
command, but after a few hours gave me the error message "Server closed the
connection unexpectedly. This probably means the server terminated
abnormall
