| From: | Chris Ernst <cernst(at)zvelo(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: VACUUM FULL freezes |
| Date: | 2013-05-23 12:04:53 |
| Message-ID: | 519E05E5.1010701@zvelo.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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. 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?
Perhaps your best option is a full dump and restore. That will
certainly de-bloat everything as well. And if you do that, you could
consider upgrading as well.
Cheers!
- Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rob Richardson | 2013-05-23 12:58:30 | What is a DO block for? |
| Previous Message | Neeraj Rai | 2013-05-23 11:53:44 | - pgaql long value corrupted using htons |