Re: Multi-tenancy with RLS

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>
Cc: Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Joe Conway <mail(at)joeconway(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Multi-tenancy with RLS
Date: 2015-09-15 19:57:14
Message-ID: CA+Tgmoa7earMWXrqfhfPFMU+O+-ObnvNUdB2UBvQfft_sPrXfA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 15, 2015 at 9:18 AM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
> Also, we've faced issues in the past with making catalog changes due to fear
> of breaking user scripts. Instead of doubling down on that with RLS on top
> of catalog tables, would it be better to move the tables to a different
> schema, make them accessible only to superusers and put views in pg_catalog?

Uggh. -1 on that option from me.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2015-09-15 20:00:53 Re: Multi-tenancy with RLS
Previous Message Jesper Pedersen 2015-09-15 19:51:38 Re: Additional LWLOCK_STATS statistics