| From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Hannes Erven <hannes(at)erven(dot)at>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Unused files in the database directory after crashed VACUUM FULL |
| Date: | 2019-02-10 15:53:03 |
| Message-ID: | 87ftsvr6e7.fsf@news-spur.riddles.org.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Hannes Erven <hannes(at)erven(dot)at> writes:
>> I've just had a "VACUUM FULL <table>" crash due to 100% disk usage.
>> Clearly my fault, I was expecting the new table to be small enough.
Tom> What do you mean by "crash" exactly? A normal transactional
Tom> failure should've cleaned up orphaned files. I suppose if the
Tom> kernel decided to kill -9 the vacuum process, that wouldn't happen
Tom> --- but that's not the usual response to out-of-disk-space.
The failure mode of this kind we see reported most often is getting a
PANIC failure from inability to extend the WAL.
--
Andrew (irc:RhodiumToad)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martín Fernández | 2019-02-10 17:32:48 | Promote replica before being able to accept connections |
| Previous Message | Tom Lane | 2019-02-10 15:41:08 | Re: Unused files in the database directory after crashed VACUUM FULL |