Hi Viorel,
what are the exact circumstances for this? I'm not experiencing
that behavior. Maybe it depends on your settings in pg_hba.conf?
And are you using -X set-session-authorization and so on?
Regards
Tino Wildenhain
Viorel Dragomir wrote:
> As i experienced with pg_dump it looks like in ver.7.3 requires interactive
> enter password for *custom users*.
>
> The 7.1 will not make this kind of problems.
>
> Still in 7.3 you can make it with cron, but as i know, only with a script
> which might look like this
>
> <?php
> exec("pg_dump -u [other options] db_name < /path_to/password_file.txt >
> the_dumped_file");
> ?>
> where password_file.txt contains:
> user_name
> user_password
>
> good luck, and if u find that i already said is wrong please notify me
> [2 days ago i've send [almost] the same problem and this is the only answer
> that i got it]
>
> ----- Original Message -----
> From: "Shridhar Daithankar" <shridhar_daithankar@persistent.co.in>
> To: "Pgsql-General" <pgsql-general@postgresql.org>
> Sent: Friday, July 18, 2003 1:35 PM
> Subject: Re: [GENERAL] Scheduled back up
>
>
>
>>On 18 Jul 2003 at 15:58, Kallol Nandi wrote:
>>
>>>How to go about scheduled backup in Postgresql.
>>
>>You need to use cron and pgdump. Man pages for both of them will give you
>
> what
>
>>you want.
>>
>>Bye
>> Shridhar
>>
>>--
>>Cohen's Law: There is no bottom to worse.
>>
>>
>>---------------------------(end of broadcast)---------------------------
>>TIP 6: Have you searched our list archives?
>>
>> http://archives.postgresql.org
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>