| From: | Joseph Kregloh <jkregloh(at)sproutloud(dot)com> |
|---|---|
| To: | Andomar <andomar(at)aule(dot)net> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Allow login on slave only |
| Date: | 2016-12-19 16:58:43 |
| Message-ID: | CAAW2xfeba05fR8NBToCEVx75vuX-aCK7+g_GB06Cr=-7415TiA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
You can leave authentication to something else. For example authenticate
the users by having them connect to pgBouncer first.
-Joseph
On Fri, Dec 16, 2016 at 11:17 AM, Andomar <andomar(at)aule(dot)net> wrote:
> We run a master server and a hot standby server. Reporting users login to
> the standby server to run long queries. However, their login is also valid
> on the master server. Is it possible to prevent a user from logging in to
> the master server?
>
>
>
> A statement like:
>
>
>
> alter role newbie_business_analyst nologin;
>
>
>
> Is replicated, so it would block logins on both servers.
>
>
>
> Thanks,
>
> Andomar
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christophe Escobar | 2016-12-19 17:05:57 | Avoid using index scan backward when limit order desc |
| Previous Message | Poul Kristensen | 2016-12-19 15:17:36 | pg_hba.conf debugging or logging when using ldag to authenticate |