Re: [BUG] Crash of logical replica with trigger.
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: "Anton A. Melnikov" <aamelnikov@inbox.ru>, pgsql-bugs@lists.postgresql.org
Date: 2022-10-07T08:40:04Z
Lists: pgsql-bugs
On Fri, Oct 07, 2022 at 05:19:46PM +0900, Masahiko Sawada wrote: > I realized that this problem is also reported in -hackers and there is > some discussion there[1]. The patch I proposed seems to be the same as > the patch Anton A. Melnikov proposed, but Tom does not like it. This patch was listed in the CF which is why I have begun poking at it. Anyway, I have the same opinion, and the first thing I was looking at are other code paths similar to the one patched here where we expect a portal to be always active :) Your patch switches a procedure path where we have assumed for years that a portal would be active in its error handling. This could hide problems in the future if for some reason this API begins to get used in the context where a portal is not active, so logical workers are IMO doing the wrong thing for the commands they are executing. Let's move the discussion to the other thread, thanks for the pointer. -- Michael
Commits
-
Avoid crash after function syntax error in a replication worker.
- dea834938005 16.0 landed
- f2dc7f9e35a2 15.1 landed
- ed019b5ef955 11.18 landed
- d9ffccf8db4b 12.13 landed
- b00f342ea0f0 13.9 landed
- 5f3cec77b1b5 10.23 landed
- 2489c38cdc58 14.6 landed