Try removing security definer ... It should work.
--
Sent from: https://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
On Mon, Nov 23, 2020 at 6:52 PM Jagmohan Kaintura
wrote:
> It doesn't works putting that block inside additional BEGIN END
>
> CREATE OR REPLACE PROCEDURE TEST_TRANSACTION(
> )
> LANGUAGE 'plpgsql'
> SECURITY DEFINER
> AS $BODY$
> DECLARE
> G_LAST_UPDATE_USER_SYSTEM VARCHAR2(6) :=
It doesn't works putting that block inside additional BEGIN END
CREATE OR REPLACE PROCEDURE TEST_TRANSACTION(
)
LANGUAGE 'plpgsql'
SECURITY DEFINER
AS $BODY$
DECLARE
G_LAST_UPDATE_USER_SYSTEM VARCHAR2(6) := 'SYSTEM';
G_LAST_UPDATE_MODULE_BATCH VARCHAR2(5) := 'BATCH';
G_CNT
On Mon, Nov 23, 2020 at 10:03 AM Jagmohan Kaintura
wrote:
> Hi ,
> The Block is only failing immediately at First COMMIT only. It's not
> supporting COMMIT. I have removed some portion of code before the second
> COMMIT.
>
Please don't top-post on the Postgres lists by the way (reply with all
p
Hi ,
The Block is only failing immediately at First COMMIT only. It's not
supporting COMMIT. I have removed some portion of code before the second
COMMIT.
On Mon, Nov 23, 2020 at 9:19 PM Adrian Klaver
wrote:
> On 11/23/20 12:36 AM, Jagmohan Kaintura wrote:
> > Hi Team,
> >
> > We have many BAT
On 11/23/20 12:36 AM, Jagmohan Kaintura wrote:
Hi Team,
We have many BATCH JOBS in Oracle which we are committing after
processing few Records. These batch Jobs process in some subsets and
call transaction control statements COMMIT in case of Success and
ROLLBACK in case of failure.
While c
Hi Team,
We have many BATCH JOBS in Oracle which we are committing after processing
few Records. These batch Jobs process in some subsets and call transaction
control statements COMMIT in case of Success and ROLLBACK in case of
failure.
While converting to POstgreSQL we converted in Same Format w
