| From: | Jeremy Schneider <schneider(at)ardentperf(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jason Myers <j(dot)myers(at)brstrat(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Orphaned relations after crash/sigkill during CREATE TABLE |
| Date: | 2020-08-20 23:50:42 |
| Message-ID: | 929b4378-e7b5-445e-5868-02c0e811ccbb@ardentperf.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 8/20/20 14:46, Tom Lane wrote:
> There might be value in a user-invokable tool that runs in an existing
> non-crashed database and looks for orphan files, but I'm not aware that
> anyone has written one. (Race conditions against concurrent table
> creation would be a problem; but probably that can be finessed somehow,
> maybe by noting the file's creation time.)
Bertrand Drouvot just put out a tool to list potentially orphaned files
a couple months ago.
https://github.com/bdrouvot/pg_orphaned
Implemented as an extension, doesn't remove the files, but useful
nonetheless.
-Jeremy
| From | Date | Subject | |
|---|---|---|---|
| Next Message | postgresdba111@outlook.com | 2020-08-21 08:19:15 | > ERROR: syntax error at or near "BYTE" |
| Previous Message | Jason Myers | 2020-08-20 22:08:32 | Re: Orphaned relations after crash/sigkill during CREATE TABLE |