Florian G. Pflug 1) postgres start/stop support 2) open ".sql" with pgadmin? 3) ssl support 4) Standard location for postgresql.conf and pg_hba.conf? 5) Nightly Builds
ad 1), 4): Depends on weather there exists a "official" binary version of postgres for OSX.
There is no official binary for OSX that I'm aware of - certainly not on the PostgreSQL ftp site anyway. However, I assume OSX uses a BSD-like init system, in which case looking for /etc/rc.d/rc.postgresql or whatever is appropriate would work for the majority of sensibly configured systems. WRT 4), again, we could just assume that installations will be in /usr/local/pgsql/data or /var/pgsql/data or whatever, as appropriate. Last time I tried that code it let me pick other locations anyway so there shouldn't be any major problems.
Hm.. no, OSX doesn't use sysv-style (or bsd-style) init-scripts. I has a quite similar system (also based on shell-scripts), but each shell-script is acompanied by a plist file, describing e.g. the dependencies. I believe that there is a api for starting and stopping services, but I'll have to check. Maybe we could add a preference specifying the servicename of postgres (since it might be PostgreSQL, or postgres, or postgresql, ...)
You are of course right for the conf-file locations - those can be choosen in pgadmin anyway, so we could just default it to some common location.
ad 2): Can you click on a saved sql query in windows, and it is opened in pgadmin3? If so, I could try to do the same for OSX
No you can't. Make it the first new feature on OSX and I'll pledge to port it to Windows :-)
The only problem I see with this, is that we would need to remember to which "Server" the sql belonged...
On a related note - I often missed the ability to switch a given sql-window to another connection (e.g. when I have to execute the same sql-script on multiple machines). Would it be possible to add a dropdrown menu to the sql-window which selects the connection to use? If I'd come up with a patch, would it be accepted?
ad 3): This is a bug in configure - but I still don't know how to fix/workaround this.
Our configure, or PostgreSQLs? Whats the problem exactly?
It the ssl-detection in the pgadmin-configure. The ssl detection works by linking with libpq, and checking if this makes the symbol SSL_connect available. On unix this works, because liking with libpq also links with libssl, which in turn provides SSL_connect. On OSX, an app may not access such a "level-2" dynamic symbol - the app needs to link to libssl directly. But then, the symbol is available, regardless of weather libpq was linked against openssl or not.
The only idea I have it to use "otool -l" (the equivalent to ldd on linux) and grep to check wether libpq links to libssl or not... but this seems to be quite... hm... hacky ;-)
greetings, Florian Pflug
smime.p7s
Description: S/MIME Cryptographic Signature
