From: | Michael Fuhr <mike(at)fuhr(dot)org> |
---|---|
To: | Zlatko Matic <zlatko(dot)matic1(at)sb(dot)t-com(dot)hr> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: automating backup ? |
Date: | 2005-06-26 12:59:14 |
Message-ID: | 20050626125914.GA78722@winnie.fuhr.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, Jun 26, 2005 at 11:18:31AM +0200, Zlatko Matic wrote:
>
> How to automate backup, so that Postgres automatically backups, for
> example, once in a week ?
Using the operating system's mechanism for scheduling jobs to run
periodically. For example, cron on Unix-like systems.
> The same question about vacuum ?
Same answer as above. See also contrib/pg_autovacuum.
> Concerning backup, how to prevent that someone makes a copy (for example
> pg_dumpall) of a database, then installs new instance of Postgres, create
> the same user acount that was the original owner and then restore the
> database. In that case all restrictions would be overriden, right ?
All what restrictions? If you've granted users permission to select
certain data, then they can copy that data to somewhere else and
do whatever they like with it; but with the original data they can
do only what you grant them permission to do. If you don't want
users to copy data then don't grant them select privilege on it,
and make sure they don't have database superuser or operating system
superuser (administrator) privileges on the database server.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2005-06-26 13:24:50 | Re: automating backup ? |
Previous Message | Zlatko Matic | 2005-06-26 09:18:31 | automating backup ? |