| From: | RDNikeAir <ryan(dot)dupuis(at)excelitas(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | VACUUM FULL freezes |
| Date: | 2013-05-22 14:49:06 |
| Message-ID: | 1369234145946-5756477.post@n5.nabble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
abnormally before or while processing the request. The connection to the
server was lost. Attempting reset: Failed." I know that the server did not
fail, so i assume that this timed out. The server is running version 7.4 (i
know it's an old version).
The database has several tables, but 99% of the data is located in a single
table. My fear is that there's not enough system memory left to perform the
full vacuum since it's all contained in a single table.
Any ideas?
--
View this message in context: http://postgresql.1045698.n5.nabble.com/VACUUM-FULL-freezes-tp5756477.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2013-05-22 16:20:45 | Re: VACUUM FULL freezes |
| Previous Message | fburgess | 2013-05-22 14:41:28 | Re: [PERFORM] Very slow inner join query Unacceptable latency. |