| From: | Marc Munro <marc(at)bloodnok(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: policies and extensions |
| Date: | 2020-02-18 23:26:17 |
| Message-ID: | 1582068377.18009.28.camel@bloodnok.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, 2020-02-18 at 15:06 -0500, Stephen Frost wrote:
>
> Policies, also being part of the overall privilege system, could
> certainly be looked at in a similar light as being different from
> triggers and indexes...
While I think I agree with Stephen here, I don't have a vested interest
in any particular solution and am not advocating for change.
I am kinda surprised that policies are not explicitly tracked as part
of an extension but I can live with the status quo now that it has been
explained.
I think it *may* be worth stating something explicitly in the
documentation but again I am not advocating.
Thanks again.
__
Marc
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2020-02-19 01:22:27 | Re: How to handle CASE statement with PostgreSQL without need for typecasting |
| Previous Message | Adrian Klaver | 2020-02-18 22:15:40 | Re: [EXTERNAL]: Re: pglogical install errors openSUSE Leap 42.1 |