2011-02-23 12:18:09 -05:00
|
|
|
/*-------------------------------------------------------------------------
|
|
|
|
|
*
|
|
|
|
|
* reltrigger.h
|
|
|
|
|
* POSTGRES relation trigger definitions.
|
|
|
|
|
*
|
|
|
|
|
*
|
2019-01-02 12:44:25 -05:00
|
|
|
* Portions Copyright (c) 1996-2019, PostgreSQL Global Development Group
|
2011-02-23 12:18:09 -05:00
|
|
|
* Portions Copyright (c) 1994, Regents of the University of California
|
|
|
|
|
*
|
|
|
|
|
* src/include/utils/reltrigger.h
|
|
|
|
|
*
|
|
|
|
|
*-------------------------------------------------------------------------
|
|
|
|
|
*/
|
|
|
|
|
#ifndef RELTRIGGER_H
|
|
|
|
|
#define RELTRIGGER_H
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* These struct really belongs to trigger.h, but we put it separately so that
|
|
|
|
|
* it can be cleanly included in rel.h and other places.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
typedef struct Trigger
|
|
|
|
|
{
|
|
|
|
|
Oid tgoid; /* OID of trigger (pg_trigger row) */
|
|
|
|
|
/* Remaining fields are copied from pg_trigger, see pg_trigger.h */
|
|
|
|
|
char *tgname;
|
|
|
|
|
Oid tgfoid;
|
|
|
|
|
int16 tgtype;
|
|
|
|
|
char tgenabled;
|
|
|
|
|
bool tgisinternal;
|
|
|
|
|
Oid tgconstrrelid;
|
|
|
|
|
Oid tgconstrindid;
|
|
|
|
|
Oid tgconstraint;
|
|
|
|
|
bool tgdeferrable;
|
|
|
|
|
bool tginitdeferred;
|
|
|
|
|
int16 tgnargs;
|
|
|
|
|
int16 tgnattr;
|
|
|
|
|
int16 *tgattr;
|
|
|
|
|
char **tgargs;
|
|
|
|
|
char *tgqual;
|
2016-11-04 11:49:50 -04:00
|
|
|
char *tgoldtable;
|
|
|
|
|
char *tgnewtable;
|
2011-02-23 12:18:09 -05:00
|
|
|
} Trigger;
|
|
|
|
|
|
|
|
|
|
typedef struct TriggerDesc
|
|
|
|
|
{
|
|
|
|
|
Trigger *triggers; /* array of Trigger structs */
|
|
|
|
|
int numtriggers; /* number of array entries */
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* These flags indicate whether the array contains at least one of each
|
|
|
|
|
* type of trigger. We use these to skip searching the array if not.
|
|
|
|
|
*/
|
|
|
|
|
bool trig_insert_before_row;
|
|
|
|
|
bool trig_insert_after_row;
|
|
|
|
|
bool trig_insert_instead_row;
|
|
|
|
|
bool trig_insert_before_statement;
|
|
|
|
|
bool trig_insert_after_statement;
|
|
|
|
|
bool trig_update_before_row;
|
|
|
|
|
bool trig_update_after_row;
|
|
|
|
|
bool trig_update_instead_row;
|
|
|
|
|
bool trig_update_before_statement;
|
|
|
|
|
bool trig_update_after_statement;
|
|
|
|
|
bool trig_delete_before_row;
|
|
|
|
|
bool trig_delete_after_row;
|
|
|
|
|
bool trig_delete_instead_row;
|
|
|
|
|
bool trig_delete_before_statement;
|
|
|
|
|
bool trig_delete_after_statement;
|
|
|
|
|
/* there are no row-level truncate triggers */
|
|
|
|
|
bool trig_truncate_before_statement;
|
|
|
|
|
bool trig_truncate_after_statement;
|
2016-11-04 11:49:50 -04:00
|
|
|
/* Is there at least one trigger specifying each transition relation? */
|
|
|
|
|
bool trig_insert_new_table;
|
|
|
|
|
bool trig_update_old_table;
|
|
|
|
|
bool trig_update_new_table;
|
|
|
|
|
bool trig_delete_old_table;
|
2011-02-23 12:18:09 -05:00
|
|
|
} TriggerDesc;
|
|
|
|
|
|
Phase 2 of pgindent updates.
Change pg_bsd_indent to follow upstream rules for placement of comments
to the right of code, and remove pgindent hack that caused comments
following #endif to not obey the general rule.
Commit e3860ffa4dd0dad0dd9eea4be9cc1412373a8c89 wasn't actually using
the published version of pg_bsd_indent, but a hacked-up version that
tried to minimize the amount of movement of comments to the right of
code. The situation of interest is where such a comment has to be
moved to the right of its default placement at column 33 because there's
code there. BSD indent has always moved right in units of tab stops
in such cases --- but in the previous incarnation, indent was working
in 8-space tab stops, while now it knows we use 4-space tabs. So the
net result is that in about half the cases, such comments are placed
one tab stop left of before. This is better all around: it leaves
more room on the line for comment text, and it means that in such
cases the comment uniformly starts at the next 4-space tab stop after
the code, rather than sometimes one and sometimes two tabs after.
Also, ensure that comments following #endif are indented the same
as comments following other preprocessor commands such as #else.
That inconsistency turns out to have been self-inflicted damage
from a poorly-thought-through post-indent "fixup" in pgindent.
This patch is much less interesting than the first round of indent
changes, but also bulkier, so I thought it best to separate the effects.
Discussion: https://postgr.es/m/E1dAmxK-0006EE-1r@gemulon.postgresql.org
Discussion: https://postgr.es/m/30527.1495162840@sss.pgh.pa.us
2017-06-21 15:18:54 -04:00
|
|
|
#endif /* RELTRIGGER_H */
|
