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 sti
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
I have
On Thu, 2009-07-23 at 19:30 -0400, Scott Holmes wrote:
> 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
>
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 sti
Hello:
I have been trying to improve the performance of my 8.3.3 postgres
database, running on solaris 10. I have been playing around with a few
configuration settings, including the shared_buffers because I have
sluggish performance when accessing some very large tables, and the
maintence_work_mem
Hi all;
looking at a system running 8.1.15
via a select from pg_stat_activity I see a row where the vcurrent_query =
'VACUUM'
I see also that autovacuum is on. Would autovacuum be running a vacuum on the
entire db? I didn't think autovacuum did that. If not, how do I know in
version 8.1 what t
