On Sat, Feb 2, 2013 at 09:55:29PM -0500, Phil Sorber wrote: > >>> I think that output is important as do others up thread. I think it'd > >>> be simpler to just disable dbname's ability to double as conninfo. If > >>> we are looking for easy, that is. > >>> > >>> I don't mind duplicating the behavior from conninfo_array_parse() or > >>> uri-regress.c either. I can just put a comment that at some point in > >>> the future we should add a libpq interface for it. > >> > >> I suggest duplicate the code for 9.3, and submit a patch to refactor > >> into a new libpq function for CF2013-next. If the patch is simple > >> enough, we can consider putting it into 9.3. > > > > Agreed. > > > > Regards, > > > > -- > > Fujii Masao > > OK, here is the patch that handles the connection string in dbname. > I'll post the other patch under a different posting because I am sure > it will get plenty of debate on it's own.
If we could run pg_isready on the patch, it would tell us if the patch is ready. Consider this a feature request. ;-) -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
