| From: | Atul Kumar <akumar14871(at)gmail(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| 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-09-02 05:11:30 |
| Message-ID: | CA+ONtZ4=73THK_Mi1-KwC6-t92VwZHyGezj9cVftna2o-fTyaA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
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(dot)albe(at)cybertec(dot)at> wrote:
> 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 | Shaish Guni | 2021-09-02 05:13:56 | Re: vacuumlo |
| Previous Message | Mukesh Rajpurohit | 2021-09-02 04:34:08 | Re: Postgresql.conf group ownership changed automatically |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shaish Guni | 2021-09-02 05:13:56 | Re: vacuumlo |
| Previous Message | Kyotaro Horiguchi | 2021-09-02 02:40:33 | Re: oldest WAL files not removed |