| From: | oleg yusim <olegyusim(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Jerry Sievers <gsievers19(at)comcast(dot)net>, Scott Mead <scottm(at)openscg(dot)com>, John R Pierce <pierce(at)hogranch(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Loggingt psql meta-commands |
| Date: | 2015-12-10 20:46:48 |
| Message-ID: | CAKd4e_GaJ7xw8Ryi0=p-NLT_a2wW5aGLz4CZKQk-1Pf-2c-2Rg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi David,
Can you, please, give me example?
Thanks,
Oleg
On Thu, Dec 10, 2015 at 2:25 PM, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Thu, Dec 10, 2015 at 1:20 PM, oleg yusim <olegyusim(at)gmail(dot)com> wrote:
>
>> Also... how do we control who can run meta commands?
>>
>
> You cannot do so directly but you can control permissions to the
> underlying schema that the meta-command queries touch so that attempting to
> run the meta-command fails.
>
> This is not as simple as it may seem; visibility of the schema is
> considerably more permissive than visibility of data.
>
> David J.
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2015-12-10 20:50:06 | Re: Loggingt psql meta-commands |
| Previous Message | David G. Johnston | 2015-12-10 20:25:42 | Re: Loggingt psql meta-commands |