| From: | Richard Guo <guofenglinux(at)gmail(dot)com> |
|---|---|
| To: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrei Lepikhov <lepihov(at)gmail(dot)com>, Greg Sabino Mullane <htamfids(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Alexander Lakhin <exclusion(at)gmail(dot)com> |
| Subject: | Re: Correction of RowMark Removal During Sel-Join Elimination |
| Date: | 2025-08-30 23:51:24 |
| Message-ID: | CAMbWs49K+N_naHTHSerYFcUD8oRcrKG+1coAHG_sjRdXg3iXtQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Aug 31, 2025 at 8:41 AM Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
> On Sun, Aug 31, 2025 at 8:12 AM Alexander Korotkov <aekorotkov(at)gmail(dot)com> wrote:
> > The same patch with a bit revised comment and commit message.
> FWIW, I reported this same issue and proposed the patch last week in
> Discussion: https://postgr.es/m/CAMbWs48x=GsGan_bvQ+j0rLqYFNi9W725EmJpWUZv1RrmaicZQ@mail.gmail.com
I think it's better to push this patch sooner rather than later, as
multiple people have encountered the issue in different ways. I'll go
ahead and push 0001 from my patch set shortly. I don't think we need
to backpatch it, since the issue only occurs after commit e2debb643.
Thanks
Richard
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2025-08-31 00:49:50 | Re: Correction of RowMark Removal During Sel-Join Elimination |
| Previous Message | Alexey Makhmutov | 2025-08-30 23:47:40 | High CPU consumption in cascade replication with large number of walsenders |