| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Atul Kumar <akumar14871(at)gmail(dot)com> |
| Cc: | Ian Dauncey <Ian(dot)Dauncey(at)bankzero(dot)co(dot)za>, "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: vacuumlo |
| Date: | 2021-08-31 08:52:10 |
| Message-ID: | 2ad9e2b296875c15d583aebc074755a613289595.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
On Tue, 2021-08-31 at 11:15 +0530, Atul Kumar wrote:
> On Tuesday, August 31, 2021, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
>
> > On Tue, 2021-08-31 at 01:11 +0530, Atul Kumar wrote:
> > You may restart the postgres services. That temp file will be deleted automatically then.
> >
> > No - orphaned files left behind from a crash will not be removed during a restart.
>
> Ok, but after restart it is safe to remove such files.
It is always save to remove those files.
The problem is to identify them.
Remove the wrong file, and your cluster is toast.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2021-09-01 06:53:52 | Re: Estimating HugePages Requirements? |
| Previous Message | Atul Kumar | 2021-08-31 05:45:20 | Re: vacuumlo |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2021-08-31 08:53:45 | Re: prevent WAL replication to fill filesystem |
| Previous Message | basti | 2021-08-31 08:36:24 | prevent WAL replication to fill filesystem |