This is what I was trying to avoid. I'd have to run the script
every five minutes, even if it isn't needed, to handle the
times when it is. That just seemed like sort of a clumsy way
to handle the problem. But perhaps this is the best
solution?
Richard
> Richard Stover <richard@ucolick.org> writes:
>
>
>> Do I have to run a small program which is setuid to the owner
>> of the tables in order to make it possible for the users to
>> VACUUM the tables? Or is there a more elegant way to do this?
>
>
> Why not run 'vacuumdb' periodically out of 'cron' as the postgres
> user?
>
> -Doug
>
>
--
Richard Stover email: richard@ucolick.org
Detector Development Laboratory http://www.ccd.ucolick.org
UCO/Lick Observatory Voice: 831-459-2139
Natural Sciences Bldg. 2, Room 160
University of California FAX: 831-459-2298
Santa Cruz, CA 95064 USA FAX: 831-426-5244 (Alternate)
----------------------------------------------------------------------