| From: | Henson Choi <assam258(at)gmail(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org>, jian(dot)universality(at)gmail(dot)com |
| Cc: | pgsql-hackers(at)postgresql(dot)org, zsolt(dot)parragi(at)percona(dot)com, sjjang112233(at)gmail(dot)com, vik(at)postgresfriends(dot)org, er(at)xs4all(dot)nl, jacob(dot)champion(at)enterprisedb(dot)com, david(dot)g(dot)johnston(at)gmail(dot)com, peter(at)eisentraut(dot)org, li(dot)evan(dot)chao(at)gmail(dot)com |
| Subject: | Re: Row pattern recognition |
| Date: | 2026-06-28 10:22:46 |
| Message-ID: | CAAAe_zBUn-+PsGLqFonWA1V4KGaPE6s-Vp85JHqu26Kv5yXMrQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>, jian(dot)universality(at)gmail(dot)com
Cc: pgsql-hackers(at)postgresql(dot)org, zsolt(dot)parragi(at)percona(dot)com,
sjjang112233(at)gmail(dot)com, vik(at)postgresfriends(dot)org, er(at)xs4all(dot)nl,
jacob(dot)champion(at)enterprisedb(dot)com, david(dot)g(dot)johnston(at)gmail(dot)com,
peter(at)eisentraut(dot)org, li(dot)evan(dot)chao(at)gmail(dot)com
Subject: Re: Row pattern recognition
In-Reply-To: <CAAAe_zCd+gzpYSsC04NsKyCJeneChVZCaBP540d0p2=
c3abvvw(at)mail(dot)gmail(dot)com>
Hi Tatsuo,
> v50-0021-adjust-rpr_base-expected-output.patch
> revert-0001-remove-incidental-changes.patch
> revert-0002-revert-mark-position-elog.patch
> revert-0003-restore-funcname-guard.patch
> revert-0004-restore-doc-line-wrapping.patch
> revert-0005-remove-exclude-ties-tests.patch
> optional-0001-include-row-positions-in-mark-position-error.patch
> optional-0002-remove-unreachable-funcname-guard.patch
> optional-0003-add-exclude-ties-test-coverage.patch
Apologies for the noise -- the nine attachments above are not a new full
patch series. They are the small auxiliary patches described in that mail
(the v50-0021 build fix plus the revert-*/optional-* hunks), meant to be
applied selectively on top of the current v50 series, not to replace it.
Because I attached them as .patch files, cfbot will treat them as the latest
patch set and try to apply them to master. They are not the series and will
fail there, so the CF entry will go red through no fault of the actual patch
-- please disregard that run.
Re-posting the full series is what restores cfbot, but a plain re-post of
v49 stays red on its own: it needs v50-0021 (the rpr_base expected-output
fix) folded in to build green. Could you re-post the series with v50-0021
applied, so cfbot tracks the right patch set and goes green again?
Sorry again for the confusion.
Best,
Henson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Lakhin | 2026-06-28 12:00:01 | Re: 035_standby_logical_decoding might fail due to FATAL message lost inside libpq |
| Previous Message | Henson Choi | 2026-06-28 10:12:22 | Re: Row pattern recognition |