| From: | Charlin Barak <charlinbarak(at)gmail(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | "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-25 15:35:17 |
| Message-ID: | CAPrg5cbEQ7=2nuWRgSH1uG7JV-=K5F=bPPvNwWUy1+0YVXgkKQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Thanks Laurenz. That works.
On Tue, Apr 24, 2018 at 4:00 PM, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Farber | 2018-04-25 15:45:39 | Same condition in the CTE and in the subsequent JOIN using it |
| Previous Message | Bruno Lavoie | 2018-04-25 15:22:27 | Failed rpm package signature checks with reposync |