Re: segmentation fault when cassert enabled
Amit Kapila <amit.kapila16@gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
To: vignesh C <vignesh21@gmail.com>
Cc: Jehan-Guillaume de Rorthais <jgdr@dalibo.com>,
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, Petr Jelinek <petr.jelinek@2ndquadrant.com>, Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
Peter Geoghegan <pg@bowt.ie>
Date: 2019-12-18T03:16:01Z
Lists: pgsql-hackers
On Tue, Dec 17, 2019 at 6:01 PM vignesh C <vignesh21@gmail.com> wrote: > > On Tue, Dec 17, 2019 at 10:09 AM Amit Kapila <amit.kapila16@gmail.com> wrote: > > > > Attached patch with updated commit message based on suggestions. I am > > planning to commit this tomorrow unless there are more comments. > > > > While testing the patch on back versions, I found that the patch does > not apply on PG 11 & PG 10 branch. Attached patch has the changes for > PG 11 & PG 10 branch. Only difference in the patch was that table_open > needed to be changed to heap_open. I have verified the patch on back > branches and found it to be working. For PG 12 & current the previous > patch that Amit need to be used, I'm not reattaching here. > Pushed. -- With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com
Commits
-
Fix subscriber invalid memory access on DDL.
- d6eca4958d78 10.12 landed
- 046830164ee4 11.7 landed
- c74111d8bd68 12.2 landed
- 04c8a69c0ccc 13.0 landed
-
Fix memory allocation mistake
- a5b95016af91 10.11 landed
- d213f3114d99 11.6 landed
- 39a6210f9e0f 12.1 landed
- d40abd5fcfb2 13.0 landed