Re: Automating backup

From: Doug McNaught <doug(at)mcnaught(dot)org>
To: Richard Sydney-Smith <richard(at)ibisau(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Automating backup
Date: 2006-02-03 10:39:30
Message-ID: 874q3g20bh.fsf@asmodeus.mcnaught.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Richard Sydney-Smith <richard(at)ibisau(dot)com> writes:

> pch := pchar('pg_dump -C -h '+host+' -U '+usr+' -p '+pswd+ ' -f
> '+bckup_path+' '+dbase);
>
> to postgres.
>
> as the operator is obviously logged in how do I
> (1) trap their user id
> (2) Send the call to pg_dump without knowing their password?
>
> I expect this is a well worn route and am hoping not to have to
> reinvent a wheel.

I don't think it's "well-worn" at all--everyone I've ever heard of
runs pg_dump from a cron script.

Why not have a shell script run by the operator that runs pg_dump and
then calls psql to insert the log record (assuming the dump succeeds)?
Putting the logic inside of the database doesn't seem to buy you
anything AFAICS.

-Doug

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2006-02-03 12:41:53 Re: PgSQL as part of commercial product
Previous Message indu ss 2006-02-03 09:12:19 error calling pgmail function