| From: | cca5507 <cca5507(at)qq(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [BUG] Take a long time to reach consistent after pg_rewind |
| Date: | 2026-04-13 13:14:19 |
| Message-ID: | tencent_DFAEC2CEDADF1400992FBCB9836ABB97D007@qq.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Possible fix:
>
> The pg_rewind use pg_current_wal_insert_lsn() to set the min recovery point, which calls
> GetXLogInsertRecPtr() and returns the latest wal insert pointer. Maybe we should use
> GetXLogInsertEndRecPtr() which returns the latest wal record end pointer.
>
> Thoughts?
Another solution:
If minRecoveryPoint is just after a xlog page header, we can move it to the begin of
the page. It's safe because we just skip the xlog page header. Do I miss something?
Attach a patch done like this.
--
Regards,
ChangAo Chen
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Introduce-GetEffectiveMinRecoveryPoint.patch | application/octet-stream | 2.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2026-04-13 13:14:41 | PGConf.dev 2026 In-Person Commitfest ready for patch submissions |
| Previous Message | André Verwijs | 2026-04-13 13:14:04 | postgresql19-server-19-alpha sles 15.7 still needs older Leap 15.6 Packages .. |