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 wrote:
> We run a master server and a hot standby server. Reporting users login to
> the standby server to run long que
"Andomar" writes:
> 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?
You could use different pg_hb
>
> 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?
>
What I do is use roles as groups, and create
On Fri, Dec 16, 2016 at 9:17 AM, Andomar 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?
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_
