Constraints also run as the user modifying a table instead of the table
Again I don't see a good reason to want to execute constraints as the
user modifying a table. But I do think there can be reasons to want to
execute them as the table owner.
To summarize, my suggestion for change is:
Execute default expressions and constraints as the owner of the table.
Execute triggers as the owner of the trigger.
In response to
pgsql-hackers by date
|Next:||From: Rod Taylor||Date: 2002-10-31 15:17:26|
|Subject: Re: setuid for defaults, constraints and triggers (Was:|
|Previous:||From: Pedro M. Ferreira||Date: 2002-10-31 14:48:53|
|Subject: Re: float output precision questions|
pgsql-general by date
|Next:||From: Ericson Smith||Date: 2002-10-31 15:04:40|
|Subject: Re: handling 20,000 connection?|
|Previous:||From: Reid Thompson||Date: 2002-10-31 14:45:10|
|Subject: Could someone post a full example of using SQL & bytea to store/retrieve