From: | Willy-Bas Loos <willybas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: temporary data after diskspace error |
Date: | 2020-01-27 19:11:13 |
Message-ID: | CAHnozTjyEodb+gu3joijHR15uCsW+x9fgHGYTxkn_heYPOzJhw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ok, thanks everyone!
Will there be a lot of downtime to delete those 90GB of temp files?
Will postgres just delete those files without processing them or should I
brace for some downtime?
Op ma 27 jan. 2020 17:15 schreef Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Willy-Bas Loos <willybas(at)gmail(dot)com> writes:
> > And also: How can i make postgres clean up the files?
> > Can it be done without restarting the cluster?
> > Will restarting it help?
>
> A restart will clean out temp files. I don't think there's any
> terribly safe way to do it without that. You could manually
> remove such files that haven't been accessed recently, but the
> risk of human error is high.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2020-01-27 20:41:21 | Re: PostgresSQL 10 on remote server - Socket is not connected (0x00002749/10057) |
Previous Message | Michael Lewis | 2020-01-27 17:59:25 | Re: temporary data after diskspace error |