From: | "Dean Gibson (DB Administrator)" <postgresql4(at)ultimeth(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: running vacuum in scripts |
Date: | 2005-09-20 18:42:07 |
Message-ID: | 433057FF.7050705@ultimeth.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
You can set up pg_hba.conf so that only certain Unix users that have
access to the local Unix PostgreSQL socket can access the database
without a password (every other process uses a TCP/IP connection); then
move the socket location to other than /tmp and restrict its access w/
Unix controls. Details are in the PostgreSQL documentation, and it
works fine.
-- Dean
On 2005-09-19 11:27, Belinda M. Giardine wrote:
>This seems like it should be a frequently asked question, but I am having
>trouble finding the answer. I am in the process of switching to using
>Postgres, and realize that I need to run vacuum analyze regularly on the
>tables. This is on a Unix system so cron is the obvious choice. The
>problem is I don't want to put the user name and password in the script.
>As far as I can tell vacuum must be run by the table or database owner.
>It wouldn't be as bad to have the password in the script if it was a
>limited permissions user. Any suggestions on the best methods?
>
>Thanks,
>Belinda
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: explain analyze is your friend
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Naeslund(t) | 2005-09-20 18:45:21 | More efficient INs when comparing two columns |
Previous Message | Oleg Bartunov | 2005-09-20 18:34:48 | Re: Slow search.. quite clueless |