TRIGGER EVENT

From: Sajeev Mayandi <Sajeev_Mayandi(at)symantec(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: TRIGGER EVENT
Date: 2013-05-30 06:16:22
Message-ID: CDCC3E72.42D4E%sajeev_mayandi@symantec.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

I am process of porting from sybase to postgresql. Is there syntax equivalent of the TRIGGER EVENT Statement (Please see the sybase help for trigger event below) in Postgresql. NOTE the TRIGGER EVENT in sybase could be used to trigger an user defined event. I am not seeing any similar syntax or any equivalent syntax which behaves similar to it.

Appreciate your help

Thanks,

Sajeev

TRIGGER EVENT statement

Use this statement to trigger a named event. The event may be defined for event triggers or be a scheduled event.

Syntax

TRIGGER EVENT event-name [ ( parm = value, ... ) ]

Parameters

* parm = value When a triggering condition causes an event handler to execute, the database server can provide context information to the event handler using the event_parameter function. The TRIGGER EVENT statement allows you to explicitly supply these parameters, to simulate a context for the event handler.

Remarks

Actions are tied to particular trigger conditions or schedules by a CREATE EVENT statement. You can use the TRIGGER EVENT statement to force the event handler to execute, even when the scheduled time or trigger condition has not occurred. TRIGGER EVENT does not execute disabled event handlers.

Each value is a string. The maximum length of each value is limited by the maximum page size specified by the -gp server option. If the length of value exceeds the page size, the string is truncated at the point at which the page is full.

Permissions

Must have DBA authority.

Side effects

None.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alvaro Herrera 2013-05-30 06:24:38 Re: TRIGGER EVENT
Previous Message Stephen Frost 2013-05-30 02:45:17 Re: ROLE based DEFAULT PRIVILEGES