| From: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com> |
|---|---|
| To: | Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: Orphaned Files in PostgreSQL |
| Date: | 2026-08-21 06:55:19 |
| Message-ID: | aof2V2jdcD67HPeO@bdtpg |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Thu, Aug 20, 2026 at 02:40:25PM +0530, Ashutosh Sharma wrote:
> Hi All,
>
> I am revisiting this thread to propose a possible fix for this known issue.
Thanks for working on this!
> This ordering guarantees that relation storage cannot become durable
> without either a durable marker or WAL capable of reconstructing that
> marker.
I wonder if logging XLOG_SMGR_CREATE before smgrcreate() could interact badly
with a concurrent checkpoint? I looked at [1] and it looks like it used a separate
PRECREATE record and kept the usual CREATE record after physical creation.
Could this be reused here, independently of the rest of its undo infrastructure?
[1]: https://postgr.es/m/CAEepm%3D0ULqYgM2aFeOnrx6YrtBg3xUdxALoyCG%2BXpssKqmezug%40mail.gmail.com
Regards,
--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2026-08-21 07:00:48 | Re: [PATCH] doc: clarify AS requirement when VALUES used in a FROM clause |
| Previous Message | Peter Smith | 2026-08-21 06:53:21 | Re: Support EXCEPT for TABLES IN SCHEMA publications |