But why should a superuser need the ACL to be applied before being allowed
access? If you make the permission-checking function check if the user is a
superuser before looking for per-user grants, wouldn't that solve the issue?
On 26 July 2017 at 16:30, Tom Lane wrote:
> Robert Haas writes:
> >
There is this problem with the jsonb operators "? text" "?| text[]"
and "?& text[]" that the question mark is typically used for prepared
statement parameters in the most used abstraction APIs in Java and
PHP.
This really needs an alternative. Something like "HAS text", "HAS
ANY(text[])" and "HAS
ating
the one search query where materialized views would be useful, because it's
heavy.
2015-05-27 13:42 GMT+03:00 Marko Tiikkaja :
> On 5/27/15 12:39 PM, Jordan Gigov wrote:
>
>> I found myself in need of triggers that are run only once per transaction,
>> rather than per
I found myself in need of triggers that are run only once per transaction,
rather than per row or statement within the transaction. Meaning it will
always be deferred and never called twice for the same transaction.
Perhaps in 9.6 this part of syntax for trigger creation can be changed from:
[ FO
