| From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: any tips to have restricted inbound and getting connected with postgresql dB |
| Date: | 2024-12-20 20:25:57 |
| Message-ID: | CANzqJaB6-FakfpM8tXJ_11gvTo65ep8M-oS4GSC1XxfBPPBZHg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Dec 20, 2024 at 2:25 PM Y_Bharani_mbsv <mailbsv(at)yahoo(dot)com> wrote:
> Team
> I have the need to have postgresql db running in multiuser mode and do my
> needed tasks for few mins.
>
> How to restrict all the application layer , not to get connected with the
> postgres db ,
> during my specific time window
>
1. Create a pg_hba_maintmode.conf with only the relevant hosts in it.
2. Copy pg_hba.conf to pg_hba_multi.conf.
3. Copy pg_hba_maintmode.conf to pg_hba.conf.
4. pg_ctl reload.
5. Use pg_stat_activity and pg_cancel_backend() to kill the application
connections.
6. Do your work.
7. Copy pg_hba_multi.conf to pg_hba.conf.
8. pg_ctl reload
Or... just shut down the user application.
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Y_Bharani_mbsv | 2024-12-20 22:49:35 | Re: any tips to have restricted inbound and getting connected with postgresql dB |
| Previous Message | Adrian Klaver | 2024-12-20 20:13:03 | Re: any tips to have restricted inbound and getting connected with postgresql dB |