Re: Using the public schema
| От | Charlin Barak |
|---|---|
| Тема | Re: Using the public schema |
| Дата | |
| Msg-id | CAPrg5cbEQ7=2nuWRgSH1uG7JV-=K5F=bPPvNwWUy1+0YVXgkKQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Using the public schema (Laurenz Albe <laurenz.albe@cybertec.at>) |
| Список | pgsql-general |
Thanks Laurenz. That works.
On Tue, Apr 24, 2018 at 4:00 PM, Laurenz Albe <laurenz.albe@cybertec.at> wrote:
Charlin Barak wrote:
> We will be developing three new applications in PostgreSQL, each having its own
> database instance running on different hosts. We will only have one schema per
> Postgres instance. The data is read-write only by one application/schema in the
> DB instance and the data is published to other applications via API calls.
>
> In such a standalone database configuration, are there any security implications
> or any downsides to creating the application in the public schema?
No, that's fine.
Just REVOKE CREATE ON SCHEMA public FROM PUBLIC.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
В списке pgsql-general по дате отправления: