On Wed, 11 Jul 2001 pgsql-bugs(at)postgresql(dot)org wrote:
> Jos Mara Fernndez Gonzlez (jmfernandez(at)cnb(dot)uam(dot)es) reports a bug
> with a severity of 2
> The lower the number the more severe it is.
> Short Description
> PL/pgSQL triggers with parameters don't work
> Long Description
> The report is for PostgreSQL 7.1.2. When you create a trigger
> which calls a function with parameters, the system links against the
> function with the same name and no parameter, and if it doesn't exist
> it tells "function doesn't exist". Tests have been made with
> PL/pgSQL-encoded functions.
Trigger functions take their arguments in a different fashion.
They should be defined as taking no regular arguments and returning
opaque and it's something like TG_ARGS in plpgsql that the create
trigger time arguments are passed in. I believe this is described in
In response to
pgsql-bugs by date
|Next:||From: Kristis Makris||Date: 2001-07-11 18:13:41|
|Subject: Re: [BUGS] ERROR: deferredTriggerGetPreviousEvent: event for tuple(0,9) not found|
|Previous:||From: Kannan The Barbarian||Date: 2001-07-11 17:57:55|
|Subject: Upgrade to 7.1.2 problem|