On 23 Mar, 19:32, [EMAIL PROTECTED] wrote:
thanks Margaret, I didn't know window scheduler so far.
By the way I have choosen to do all management stuff on database via
command line programs, providing passowd file for administrator user.
Thanks
Filippo
---(end of broad
> Date: 21 Mar 2007 00:29:33 -0700
> From: "filippo" <[EMAIL PROTECTED]>
> To: pgsql-general@postgresql.org
> Subject: Re: shell script to SQL statement: `pg_dump | psql -U`
> Message-ID: <[EMAIL PROTECTED]>
>
> On 20 Mar, 16:47, [EMAIL PROTECTED] (Tom Lane) wrote:
> > "filippo" <[EMAIL PROTECTED]
On 20 Mar, 16:47, [EMAIL PROTECTED] (Tom Lane) wrote:
> "filippo" <[EMAIL PROTECTED]> writes:
> > The problem with the current implementation is that sometime pd_dump
> > and psql ask for password but I want to create the database copy
> > without any user typing (it is a cron script).
>
> Create a
filippo wrote:
The problem with the current implementation is that sometime pd_dump
and psql ask for password but I want to create the database copy
without any user typing (it is a cron script)
Consider using the PGPASSWORD environment variable or .pgpass file.
--
Richard Huxton
Archonet
"filippo" <[EMAIL PROTECTED]> writes:
> The problem with the current implementation is that sometime pd_dump
> and psql ask for password but I want to create the database copy
> without any user typing (it is a cron script).
Create a ~/.pgpass file for the user that runs the cron job.
I have a perl program that I use (also) to copy a database to a
perfect clone having a different name. To perform the operation I
execute from perl the following shell pipe
pg_dump -U postgres -h db_server database_name | psql -U postgres -h
db_server database_name_backup
I'd like to perform the
