Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> Notes: As the syntax shows, these would be statement-level triggers
> (only). Requesting row level triggers will cause an error. [As Chris
> Browne explained, if people really want, they can use these facilities
> to create a Before Statement trigger that executes a DELETE, which then
> fires row level calls.]
Is there a way for a BS trigger to return a flag "skip the statement",
as there is for BR?
> I also plan to add a TRUNCATE privilege, though that will be a separate
> patch in a later post. That will widen the use case of TRUNCATE, which
> should be OK to do once we've covered the replication concerns.
Considering it's not MVCC-safe, do we *want* to widen the use case?
There are way too many table privilege bits already; to add more you
need something a lot stronger than a "might be nice" argument.
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Wes||Date: 2008-01-25 16:14:04|
|Subject: Re: REINDEX on large DB vs. DROP INDEX/CREATE INDEX|
|Previous:||From: Andrew Dunstan||Date: 2008-01-25 15:11:49|
|Subject: Re: plperl: Documentation on BYTEA decoding is wrong|