From: Tom Lane <tgl@sss.pgh.pa.us>
To: Pepe TD Vo <pepevo@yahoo.com>
cc: Pgsql-admin <pgsql-admin@postgresql.org>, pgsql-sql@postgresql.org
Subject: Re: Automatically updating a new information column in PostgreSQL
In-reply-to: <744670167.2325583.1570195612720@mail.yahoo.com>
References: <744670167.2325583.1570195612720.ref@mail.yahoo.com>
 <744670167.2325583.1570195612720@mail.yahoo.com>
Comments: In-reply-to Pepe TD Vo <pepevo@yahoo.com>
	message dated "Fri, 04 Oct 2019 13:26:52 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <5215.1570197015.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 04 Oct 2019 09:50:15 -0400
Message-ID: <5216.1570197015@sss.pgh.pa.us>
Precedence: bulk

Pepe TD Vo <pepevo@yahoo.com> writes:
> good morning experts,I have a trigger before insert (even with or update=
) and seem it doesnt' work.=C2=A0 The function simply sets both columns na=
med mig_filename to "unknown if its null, and mig_insert_dt to current tim=
estample for each row passed to the trigger.
> here is my script even I take all the rest out and just simple function =
with new.mig_insert_dt :=3D localtimestamp;

It looks like the RETURN NEW is inside the exception handler recovery
block, which is not where you want it.  When I run this example I get

ERROR:  control reached end of trigger procedure without RETURN
CONTEXT:  PL/pgSQL function "ECISDRDM"."TRIGGER_FCT_TR_STG_APPLICATION_CDI=
M_INS"()

So there is something seriously wrong with however you are testing
this, if you failed to notice that.

			regards, tom lane