Re: psql commandline conninfo

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
Cc: "Casey Duncan" <casey(at)pandora(dot)com>, "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: psql commandline conninfo
Date: 2006-12-13 03:36:09
Message-ID: 202.1165980969@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

"Andrew Dunstan" <andrew(at)dunslane(dot)net> writes:
> We change libpq from time to time. Besides, how many DBs are there that
> match the name pattern /^conn:.*=/ ? My guess is mighty few. So I don't
> expect lots of surprise.

Um, but how many DB names have an "=" in them at all?

Basically what this proposal is about is migrating from separated
dbname/user/host/port/etc parameters to a unified conninfo parameter.
That seems to me like a good long-term objective, and so I'm willing
to break a few eggs on the way to the omelet, as long as we're not
breaking any very likely usages.

So: who here has a database with "=" in the name? And hands up if
you've got a database whose name begins with "conn:"?

I'm betting zero response rate on both of those, so see no reason to
contort the long-term definition for a very marginal difference in
the extent of backwards compatibility ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Glaesemann 2006-12-13 03:37:08 Re: Better management of mergejoinable operators
Previous Message Michael Glaesemann 2006-12-13 03:33:34 Re: Better management of mergejoinable operators

Browse pgsql-patches by date

  From Date Subject
Next Message Jim C. Nasby 2006-12-13 06:32:43 Re: Load distributed checkpoint
Previous Message Andrew Dunstan 2006-12-13 02:22:57 Re: psql commandline conninfo