| From: | John Morris <john(dot)morris(at)crunchydata(dot)com> |
|---|---|
| To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Michael Paquier <michael(at)paquier(dot)xyz>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Atomic ops for unlogged LSN |
| Date: | 2023-07-20 23:13:29 |
| Message-ID: | BYAPR13MB2677ED1797C81779D17B414CA03EA@BYAPR13MB2677.namprd13.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Based on your feedback, I’ve updated the patch with additional comments.
1. Explain the two cases when writing to the control file, and
2. a bit more emphasis on unloggedLSNs not being valid after a crash.
Thanks to y’all.
* John
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Use-atomic-ops-for-unloggedLSNs.patch | application/octet-stream | 3.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2023-07-20 23:36:37 | Re: Row pattern recognition |
| Previous Message | David Rowley | 2023-07-20 22:35:05 | Re: Performance degradation on concurrent COPY into a single relation in PG16. |