Bug#340162: postgresql-common: Add option to specify client versions for remote server access

2005-12-06 Thread Markus Schaber
Hi, Martin, Martin Pitt wrote: Right, thanks for that hint. Humm, how is that solved in URL standards? AFAIK IPv6 adresses in URLs have to be enclosed in brackets, right? E. g. [1234::1:1]:5432. AFAIR yes. SSH alternatively allows to split host and port with a / for the -L and -R options. A

Bug#340162: postgresql-common: Add option to specify client versions for remote server access

2005-11-24 Thread Martin Pitt
Hi Markus! Markus Schaber [2005-11-21 13:28 +0100]: But I have a little problem: When connecting to remote servers via -h -p -U options, I did not find any possibility to specify which client version to use (I currently have all three versions of postgresql-client installed, as we have

Bug#340162: postgresql-common: Add option to specify client versions for remote server access

2005-11-24 Thread Markus Schaber
Hi, Martin, Martin Pitt wrote: Oh, right now it uses the latest version if you don't have any local clusters, or the version of your default cluster if you have local clusters. Okay, that explains that I always get the 7.4 clients. It's not that critical, since the client ABI is the same

Bug#340162: postgresql-common: Add option to specify client versions for remote server access

2005-11-21 Thread Markus Schaber
Package: postgresql-common Version: 32 Severity: normal Hello, It is a gread idea to allow several clusters and several postgresql servers coexist together, thanks for that work! In our house, we have to manage several existing postgresql deployments of different versions in parallel. But I