Re: vacuumlo - Mailing list pgsql-admin

From Atul Kumar
Subject Re: vacuumlo
Date
Msg-id CA+ONtZ4=73THK_Mi1-KwC6-t92VwZHyGezj9cVftna2o-fTyaA@mail.gmail.com
Whole thread Raw
In response to Re: vacuumlo  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: vacuumlo  (Shaish Guni <gunisguni2007@gmail.com>)
Re: vacuumlo  (Guillaume Lelarge <guillaume@lelarge.info>)
List pgsql-admin
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

pgsql-admin by date:

Previous
From: Mukesh Rajpurohit
Date:
Subject: Re: Postgresql.conf group ownership changed automatically
Next
From: Shaish Guni
Date:
Subject: Re: vacuumlo