| From: | Nitin Jadhav <nitinjadhavpostgres(at)gmail(dot)com> |
|---|---|
| To: | Kirill Reshke <reshkekirill(at)gmail(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: Fix crash during recovery when redo segment is missing |
| Date: | 2025-12-08 04:38:00 |
| Message-ID: | CAMm1aWYAdDa81Fs_upFLFr4AczxXvoYG7t2SYyM1n8vf4ymzBw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
Thanks for reviewing and sharing your feedback.
> 1) Please do not top-post on these lists
Apologies for that. I will make sure to follow this going forward.
> 2) I did not get the exact reason this thread is different from [0]
The purpose of this thread was to share the actual patch addressing
the crash scenario discussed in [0]. That said, I agree I should have
posted the patch in [0] itself. I will make sure to use existing
threads wherever possible going forward.
Best Regards,
Nitin Jadhav
Azure Database for PostgreSQL
Microsoft
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2025-12-08 04:40:16 | Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring |
| Previous Message | shveta malik | 2025-12-08 04:36:21 | Re: Fix LOCK_TIMEOUT handling in slotsync worker |