Bear Giles writes:
> The server policy is easy to handle - it would probably go into a
> new text configuration file pg_ssl.conf.
postgresql.conf should serve you fine.
> The client policy is much harder to handle, since the details need
> to be hidden in the libpg library. I know how to handle this on
> Unix systems, but what about clients on other platforms? E.g., on
> a Windows box I would expect this information to be maintained in
> the registry, not a config file....
For libpq, put the required files in the home directory or some directory
under the home directory. That should be acceptable on Windows, too, for
now. ODBC and JDBC have their own way of storing client side
configuration, which you can discuss with their teams.
Peter Eisentraut peter_e(at)gmx(dot)net
In response to
pgsql-hackers by date
|Next:||From: Peter Eisentraut||Date: 2003-01-05 02:12:05|
|Subject: Re: Upgrading rant. |
|Previous:||From: Marc G. Fournier||Date: 2003-01-05 01:51:50|
|Subject: Re: New Portal in Place, DNS switched ...|