Joe Conway <m...@joeconway.com> writes: > On 09/15/2015 10:58 AM, Robert Haas wrote: >> I can't argue with that, I suppose, but I think row_security=force is >> a pretty useful convenience. If we must remove it, so be it, but I'd >> be a little sad.
> There are use cases where row_security=force will be set in production > environments, not only in testing. What cases, exactly, and is there another way to solve those problems? I concur with Noah's feeling that allowing security behavior to depend on a GUC is risky. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers