Re: requests / suggestions to help with backups

From: Bruno Wolff III <bruno(at)wolff(dot)to>
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-17 18:50:23
Message-ID: 20070217185023.GA23371@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Feb 15, 2007 at 22:39:13 -0500,
Lou Duchez <lou(at)paprikash(dot)com> wrote:
>
> 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;
> it sure would be nice if I could neuter my "trusted" user so he cannot
> do any damage. (Yes, I could set read-only privileges on a table-by-table
> basis. Obviously, that's a pain.)

You can use ident authentication instead of trust. That may make using the
postgres db account for the cronjob's connection an acceptible risk.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Rob Tester 2007-02-17 18:56:51 Re: Help with an index and the optimizer
Previous Message Rob Tester 2007-02-17 18:44:20 Re: Problem with index not always being used