| From: | Duncan Sands <duncan(dot)sands(at)deepbluecap(dot)com> |
|---|---|
| To: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, 'Amit Kapila' <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com> |
| Subject: | Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 |
| Date: | 2025-05-21 13:27:31 |
| Message-ID: | 75edd9d3-d861-4dd0-b190-180cc034ceba@deepbluecap.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> Based on the analysis, I created a PoC which avoids the repalloc().
> Invalidation messages distributed by SnapBuildDistributeSnapshotAndInval() are
> skipped to add in the list, just queued - repalloc can be skipped. Also, the function
> distributes messages only in the list, so received messages won't be sent again.
>
> Now a patch for PG17 is created for testing purpose. Duncan, can you apply this and
> confirms whether the issue can be solved?
Thanks Hayato Kuroda, will do, however it may take a few days.
Best wishes, Duncan.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2025-05-21 15:53:11 | Re: BUG #18931: Access to source rpms is not possible |
| Previous Message | Hayato Kuroda (Fujitsu) | 2025-05-21 11:48:12 | RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 |