From: | "Ian Harding" <harding(dot)ian(at)gmail(dot)com> |
---|---|
To: | "Lou Duchez" <lou(at)paprikash(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: requests / suggestions to help with backups |
Date: | 2007-02-16 20:07:42 |
Message-ID: | 725602300702161207i701a44e2x992bf01c349c697e@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2/16/07, Lou Duchez <lou(at)paprikash(dot)com> wrote:
> Like everyone else, I use pg_dump for backup purposes; I have a cron job
> that runs a pg_dump whose output is then FTP'd elsewhere. Two things
> that would make my life easier:
>
> 1) "grant select on database ..." or, hypothetically, "grant select on
> cluster". The goal would be to create a read-only PostgreSQL user, one
> who can read the contents of an entire database (or even the entire
> cluster) but make no changes. Currently, to do my cron job, I have to
> specify a "trusted" user, otherwise PostgreSQL will ask for a password;
A .pgpass file can fix this... I don't know if that gets you any
closer to your objective.
- Ian
From | Date | Subject | |
---|---|---|---|
Next Message | Vladimir Zelinski | 2007-02-16 20:32:28 | values from now() in the same transaction |
Previous Message | Ian Harding | 2007-02-16 17:52:18 | Re: problems: slow queries with tsearch2 |