| From: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
|---|---|
| To: | Tender Wang <tndrwang(at)gmail(dot)com> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: wrong results: merge when not matched by source |
| Date: | 2026-09-23 09:01:27 |
| Message-ID: | CAEZATCUeSmRAC-5mo5gT5XKrMM9AEYLZ2vwDVXoOxNHSHCLKKg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sun, 20 Sept 2026 at 02:41, Tender Wang <tndrwang(at)gmail(dot)com> wrote:
>
> Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> 于2026年9月19日周六 16:43写道:
> > OK, here is an update doing that.
> >
> > Since a new v19 beta is about to be released, I'll hold off on pushing
> > this until later next week.
Pushed and back-patched to v17.
> By the way, since you are looking at MERGE, I wonder if you might also
> have a chance to look at the other issue reported earlier involving a
> prepared MERGE in [1].
> I am not even sure whether the reported behavior should be considered a bug.
> I proposed a tentative fix in that thread, but I would appreciate your
> thoughts on both the expected behavior and the proposed approach.
>
> [1] https://www.postgresql.org/message-id/19689-0a1b106035cd8a5b%40postgresql.org
I'll try and have a look.
Regards,
Dean
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2026-09-23 13:34:10 | Re: TID Range Scans can return wrong results after scanning backwards |
| Previous Message | Daniel Gustafsson | 2026-09-23 07:15:47 | Re: BUG #19711: SSH tunnel with PPK identity file fails/crashes in newer pgAdmin version but works in older version |