On 7/10/2004 7:55 PM, Darcy Buskermolen wrote:

> On July 10, 2004 01:14 pm, Erik G. Burrows wrote:
>> Sure, no problem. For my education, what made changing argv a headache?
>>
>> -Erik
>>
>> > On 7/10/2004 1:47 PM, Erik G. Burrows wrote:
>> > > I've only been using Slony-I for a few days, but I already love it!
>> > > It's going to make database migrations and upgrades much, much easier.
>> > > However, I didn't like the fact that the PostgreSQL connection string
>> > > passed to the slon process shows up in 'ps' output.
>> > >
>> > > Attached is my patch to slon.c to erase the argv entry with the
>> > > connection string after slon finishes processing it's arguments, and
>> > > restore it in case of a restart. I'm not sure how portable this fix is,
>> > > but it should work on most *nix platforms, I think. I hope you find it
>> > > useful.
>> >
>> > We know from the PostgreSQL main project how much of a headache mucking
>> > with the commandline arguments is. I would much more prefer changing the
>> > slony commandline into taking a filename argument where to find all the
>> > configuration parameters that are now passed with switches. Would you be
>> > willing to rework it into something like that?
> 
> 
> My understanding is the existing .pgpass (More information can be found at 
> http://www.postgresql.org/docs/7.4/static/libpq-pgpass.html) already does 
> this for us.
> 

I thought there was a bug that caused .pgpass to be ignored when using 
conninfo for past releases.


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck at Yahoo.com #