| From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
|---|---|
| To: | japinli(at)hotmail(dot)com |
| Cc: | mats(dot)kindahl(at)gmail(dot)com, suryapoondla4(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_rewind does not rewind diverging timelines |
| Date: | 2026-06-01 06:30:58 |
| Message-ID: | 20260601.153058.2271004477925758292.horikyota.ntt@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Sorry, I only just noticed this thread.
I may be missing something, but UUID feels somewhat heavyweight to me
for this problem.
I wonder whether strengthening the history-based matching would be
sufficient instead. If timelines with the same TLI but different
histories can be treated as distinct and pg_rewind continues walking
the history chain until it finds a common ancestor, that seems like a
fairly natural fit with the existing timeline model.
UUIDs would certainly make identification straightforward, although
they would also introduce longer identifiers that are a bit less
convenient for humans to work with. My initial thought is that it may
be worth exploring how far we can get with the existing history
information before introducing a new identifier.
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chengpeng Yan | 2026-06-01 06:32:20 | Re: Extended statistics improvement: multi-column MCV missing values |
| Previous Message | Ajin Cherian | 2026-06-01 06:29:52 | Re: [PATCH] Fix NULL dereference in subscription REFRESH on concurrent DROP |