Re: newbie Administrator
| От | Lacey Powers |
|---|---|
| Тема | Re: newbie Administrator |
| Дата | |
| Msg-id | 4A68FF87.8000806@commandprompt.com обсуждение исходный текст |
| Ответ на | newbie Administrator (Scott Holmes <scott.holmes@AMBERReady.com>) |
| Список | pgsql-admin |
Hello Scott,
Hm. Having no pg_hba.conf file definitely sounds odd.
I'd try this command while logged in via psql:
SHOW hba_file;
The output should show you the path to the pg_hba.conf file, which you can then edit to limit the connections to the database.
Hope that helps. =)
Lacey
Hm. Having no pg_hba.conf file definitely sounds odd.
I'd try this command while logged in via psql:
SHOW hba_file;
The output should show you the path to the pg_hba.conf file, which you can then edit to limit the connections to the database.
Hope that helps. =)
Lacey
I have recently inherited a Linux server running pgsql and need to lock someone out but have so far been unsuccessful.
I have changed the Linux passwords
I have changed the passwords on the 3 users listed on the Database
Now the problem is the person (server) I need to block access can still connect to the database. I have verified this by changing a record in the database and the changes were reflected on the other server. I looked for pg_hba.conf and there isn’t one that I can find so I am wondering if it is a persistent connection and if it is how do I kill it? Will restarting the server drop the connection
-- Lacey Powers The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564 ext 104 PostgreSQL Replication, Consulting, Custom Development, 24x7 support
В списке pgsql-admin по дате отправления: