From: | Michael Nolan <htfoot(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Blocking access by remote users for a specific time period |
Date: | 2014-12-14 06:38:19 |
Message-ID: | CAOzAquKjAjTdgPd_zLn0dEfy0NCApUQOeTnbB7dg5cEHwU=Khg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(dot)klaver(at)aklaver(dot)com>
wrote:
>
> 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?
>>
>
> 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 ?
>
> --
>> Mike Nolan
>>
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andy Colson | 2014-12-14 15:44:18 | Re: Error: "Out of memory while reading tuples." in pushing table from SAS to PostgreSQL on Mac |
Previous Message | Adrian Klaver | 2014-12-14 05:16:21 | Re: Error: "Out of memory while reading tuples." in pushing table from SAS to PostgreSQL on Mac |