| From: | Chris Travers <chris(dot)travers(at)adjust(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Orphaned files in base/[oid] |
| Date: | 2017-08-17 05:09:24 |
| Message-ID: | CAN-RpxA1NwmfQ_MboT=v=KuSBvc=1xwdp76trr4VxvGH48bizA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 16, 2017 at 7:15 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
>
>
> I think this entirely is the wrong approach. We shouldn't add weird
> check commands that require locks on pg_class, we should avoid leaving
> the orphaned files in the first place. I've upthread outlined
> approached how to do so.
>
And in the mean time I suppose there is no reason that the approach I have
outlined cannot be used by an external program. I think it is sane to
draw the line at having the db responsible for cleaning up after itself
when something goes wrong and leave external programs to do after-the-fact
review and cleanup.
>
> Greetings,
>
> Andres Freund
>
--
Best Regards,
Chris Travers
Database Administrator
Tel: +49 162 9037 210 | Skype: einhverfr | www.adjust.com
Saarbrücker Straße 37a, 10405 Berlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-08-17 05:13:14 | Re: Quorum commit for multiple synchronous replication. |
| Previous Message | Masahiko Sawada | 2017-08-17 05:08:33 | Re: Quorum commit for multiple synchronous replication. |