From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Client application name |
Date: | 2009-10-15 16:09:01 |
Message-ID: | 1359.1255622941@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dave Page <dpage(at)pgadmin(dot)org> writes:
> Looking further, I think this might be quite clean:
> - Add a precedence flag to PQconninfoOption
> - In conninfo_parse, in the section that grabs the envvars for empty
> params, modify the logic to override any existing values if a value is
> set in the environment and the precedence flag is set for that option.
> That may be useful in the future for other options, and will certainly
> be less ugly than special casing one setting.
Changing PQconninfoOption would be an ABI break necessitating a soname
bump and recompiling all libpq-using applications. If there were a
significant probability that we'd have additional options in future that
should act this way, it might be worth it. But I don't think there is.
The approach with two different conninfo options is really probably the
logically cleanest answer short of an ABI break.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Mielke | 2009-10-15 16:23:31 | Re: Rejecting weak passwords |
Previous Message | Dave Page | 2009-10-15 15:46:57 | Re: Client application name |