pgsql: Error when a specified connection service is not found, instead

Started by Peter Eisentrautover 16 years ago4 messagescomitters
Jump to latest
#1Peter Eisentraut
peter_e@gmx.net

Log Message:
-----------
Error when a specified connection service is not found, instead of ignoring it

Modified Files:
--------------
pgsql/src/interfaces/libpq:
fe-connect.c (r1.379 -> r1.380)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/fe-connect.c?r1=1.379&r2=1.380)

#2Simon Riggs
simon@2ndQuadrant.com
In reply to: Peter Eisentraut (#1)
Re: pgsql: Error when a specified connection service is not found, instead

On Sun, 2009-11-29 at 20:14 +0000, Peter Eisentraut wrote:

Log Message:
-----------
Error when a specified connection service is not found, instead of ignoring it

Will this be backpatched? Seems like an error or all the way.

--
Simon Riggs www.2ndQuadrant.com

#3Andrew Dunstan
andrew@dunslane.net
In reply to: Simon Riggs (#2)
Re: pgsql: Error when a specified connection service is not found, instead

Simon Riggs wrote:

On Sun, 2009-11-29 at 20:14 +0000, Peter Eisentraut wrote:

Log Message:
-----------
Error when a specified connection service is not found, instead of ignoring it

Will this be backpatched? Seems like an error or all the way.

That would be a behaviour change which could conceivably break working
apps (albeit the fix would be trivial).

cheers

andrew

#4Simon Riggs
simon@2ndQuadrant.com
In reply to: Andrew Dunstan (#3)
Re: pgsql: Error when a specified connection service is not found, instead

On Mon, 2009-11-30 at 09:27 -0500, Andrew Dunstan wrote:

Simon Riggs wrote:

On Sun, 2009-11-29 at 20:14 +0000, Peter Eisentraut wrote:

Log Message:
-----------
Error when a specified connection service is not found, instead of ignoring it

Will this be backpatched? Seems like an error or all the way.

That would be a behaviour change which could conceivably break working
apps (albeit the fix would be trivial).

It seems unlikely that anybody that now has a working system will find
it broken after this change. But it seems very likely that in future
people will be caught by earlier versions, once they get used to an
error message in the later versions.

--
Simon Riggs www.2ndQuadrant.com