Re: vacuumlo - Mailing list pgsql-admin

From Shaish Guni
Subject Re: vacuumlo
Date
Msg-id CAPorVFGMLuYJT+zH89dLqhrGvwbqFkMhcAStfT7YD+hVt+EWPg@mail.gmail.com
Whole thread Raw
In response to Re: vacuumlo  (Atul Kumar <akumar14871@gmail.com>)
List pgsql-admin
You are right 


On Thu, Sep 2, 2021 at 10:56 AM Atul Kumar <akumar14871@gmail.com> wrote:
Hi,

Don’t you think it as a drawback of postgres that such temporary files don’t get deleted automatically once the transaction gets committed or rolled back .

Could you suggest a good permanent solution for such case.



Regards 
Atul






On Tuesday, August 31, 2021, Laurenz Albe <laurenz.albe@cybertec.at> wrote:
On Tue, 2021-08-31 at 11:15 +0530, Atul Kumar wrote:
> On Tuesday, August 31, 2021, Laurenz Albe <laurenz.albe@cybertec.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

--
Shaish Guni

pgsql-admin by date:

Previous
From: Atul Kumar
Date:
Subject: Re: vacuumlo
Next
From: Guillaume Lelarge
Date:
Subject: Re: vacuumlo