| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Charlin Barak <charlinbarak(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Using the public schema |
| Date: | 2018-04-24 20:00:47 |
| Message-ID: | 1524600047.2271.3.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | 范国腾 | 2018-04-25 00:31:16 | 答复: [ClusterLabs] Postgres PAF setup |
| Previous Message | Vick Khera | 2018-04-24 18:05:34 | Re: Backup Strategy Advise |