On Fri, Jun 21, 2019 at 3:45 AM RekGRpth wrote:
> >It is not plpgsql's job to clean up after other backend subsystems
> during a transaction abort.
> But plpgsql do clean up on success! I suggest only do cleanup and on
> exception.
Except that's wrong, because when an error happens, cleanup is -
>It is not plpgsql's job to clean up after other backend subsystems
during a transaction abort.
But plpgsql do clean up on success! I suggest only do cleanup and on
exception.
чт, 20 июн. 2019 г. в 20:33, Tom Lane :
> RekGRpth writes:
> > A patch fixing this bug
> >
> https://www.postgresql.org
RekGRpth writes:
> A patch fixing this bug
> https://www.postgresql.org/message-id/flat/15738-21723084f3009ceb%40postgresql.org
I do not think this code change is necessary or appropriate.
It is not plpgsql's job to clean up after other backend subsystems
during a transaction abort. Maybe if plp
A patch fixing this bug
https://www.postgresql.org/message-id/flat/15738-21723084f3009ceb%40postgresql.org
From 0144733c9f128108670f3654605f274928d83096 Mon Sep 17 00:00:00 2001
From: RekGRpth
Date: Fri, 26 Apr 2019 15:35:30 +0500
Subject: Disconnect from SPI manager on error
diff --git a/src
