| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
| Cc: | Amul Sul <sulamul(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Make relfile tombstone files conditional on WAL level |
| Date: | 2022-05-16 09:53:23 |
| Message-ID: | CA+hUKGJUyXptr_igUuw_pxV_yUyKOsUEtv4-sMCmn0Nq98p3Zg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I think you can get rid of SYNC_UNLINK_REQUEST, sync_unlinkfiletag,
mdunlinkfiletag as these are all now unused.
Are there any special hazards here if the plan in [1] goes ahead? If
the relfilenode allocation is logged and replayed then it should be
fine to crash and recover multiple times in a row while creating and
dropping tables, with wal_level=minimal, I think. It would be bad if
the allocator restarted from a value from the checkpoint, though.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2022-05-16 10:34:31 | Re: Remove support for Visual Studio 2013 |
| Previous Message | Peter Smith | 2022-05-16 09:23:14 | Re: Skipping schema changes in publication |