Jim C. Nasby wrote:
On Sat, Feb 18, 2006 at 02:49:08PM -0500, Tom Lane wrote:
Perhaps we should make a concerted effort to split the libpq docs into a
section for programmers vs one for users, the latter part covering
the libpq behavior that is interesting to users of a libpq-based app.
On Sat, Feb 18, 2006 at 02:49:08PM -0500, Tom Lane wrote:
Perhaps we should make a concerted effort to split the libpq docs into a
section for programmers vs one for users, the latter part covering
the libpq behavior that is interesting to users of a libpq-based app.
.pgpass, pg_service, the
Hi,
A little while ago there was someone asking for tools to make it easier
to connect to multiple servers. It occured to me that it might be
useful to have a config file the way ssh does it:
Host production
ServerName db1
DBName main
Usernameblah
Passwordblah
UseSSL
Martijn van Oosterhout wrote:
A little while ago there was someone asking for tools to make it
easier to connect to multiple servers. It occured to me that it might
be useful to have a config file the way ssh does it:
That looks suspiciously like the service facility that we already have.
--
Michael Fuhr wrote:
On Sat, Feb 18, 2006 at 07:52:22PM +0100, Martijn van Oosterhout wrote:
A little while ago there was someone asking for tools to make it easier
to connect to multiple servers. It occured to me that it might be
useful to have a config file the way ssh does it:
Andrew Dunstan [EMAIL PROTECTED] writes:
This needs a LOT more prominence. We probably need to refer to these
things on the manual pages for each of the libpq clients we have.
Haven't we learned that lesson from .pgpass ? The number of people who
read the libpq docs is probably vanishingly
On Sat, Feb 18, 2006 at 12:19:39PM -0700, Michael Fuhr wrote:
On Sat, Feb 18, 2006 at 07:52:22PM +0100, Martijn van Oosterhout wrote:
A little while ago there was someone asking for tools to make it easier
to connect to multiple servers. It occured to me that it might be
useful to have a
