Re: Blocking access by remote users for a specific time period
| От | Michael Nolan |
|---|---|
| Тема | Re: Blocking access by remote users for a specific time period |
| Дата | |
| Msg-id | CAOzAquKjAjTdgPd_zLn0dEfy0NCApUQOeTnbB7dg5cEHwU=Khg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Blocking access by remote users for a specific time period (Adrian Klaver <adrian.klaver@aklaver.com>) |
| Ответы |
Re: Blocking access by remote users for a specific time period
Re: Blocking access by remote users for a specific time period |
| Список | pgsql-general |
Yeah, a cron job to swap pg_hba.conf files is the best solution I've come up with so far. It's not one web app, it's closer to two dozen of them, on multiple sites.
--
Mike Nolan--
On Sat, Dec 13, 2014 at 11:10 PM, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
Use a cron job that at beginning of period swaps out the pg_hba.conf with one that denies access, reloads server and then at end of time period reverse procedure ?On 12/13/2014 08:13 PM, Michael Nolan wrote:I have several web apps that access our Postgresql database that I'd
like to lock out of the database for about an hour during a weekly
maintenance interval. (There are some internal users that do not get
locked out, because they're running the maintenance tasks.)
There are no time-of-day access limitation parameters in the pg_hba.conf
file, are there any simple ways to do this?--
Mike Nolan
--
Adrian Klaver
adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: