Craig Ringer wrote:
I'm hesitant to agree with this the PG installer doing more automatically. If the user does not understand security and proper configuration to get it to work on windows client, the server setup will be poorly configured with security problems that a MAC truck can drive through.On Fri, 2009-06-19 at 01:03 -0400, Tom Lane wrote:I see lots of questions here that seem to be related to (a) virus scanner interference and (b) installation/reinstallation. Lots of the reinstall issues seem to be with people who don't really understand NT users, ACLs, etc and aren't really competent to admin a machine, but they do make me wonder if the Pg installer can do more to help them out, eg: Example is MS itself and CAD developers. I have yet to see a CAD program that does not require to run with Administrator security credentials. MS with many of its Server Programs does similar stuff now that PG does automatically creates users sets up the directory/registry security. Its really easy to trash those setting keeping the app from working. You hear about the same problems many people talk about hear as they do with the other databases running on windows see http://support.microsoft.com/kb/309422 http://support.microsoft.com/kb/287932 http://msdn.microsoft.com/en-us/library/ms175043.aspx The only thing i think that would make sense, is to have the installer add exceptions to the windows firewall for the Postgresql ports. This is the same problem MSSQL has on reinstall except it just creates new directories and Security Credentials automatically. I have seen computers with 5 SQLServer user accounts."The data directory you have specified (C:\PgData) already exists, but cannot be accessed by the user you want to run PostgreSQL as. Would you like to: [a] use a new data directory, [b] grant the postgresql user the rights to access the data directory you have specified, or [c] change the user you start PostgreSQL as to the user owning the data directory ? [clean install to new directory][grant access to old directory][change postgresql user][cancel installation]" along with lots of other crap laying around PG install does lots of the stuff for the user but does not do everything as many installers do which can leave the OS install a complete and utter mess requiring reformat and reinstall to get it to work at all. Or leaves that applications install such tangle mess its impossible to figure out what the user did. I can read it know "Postgresql gurus i go to the PGDATA directory and find it has PGDATA though PGDATA_8 how do i tell which is the current data directory." I have suffered this question with MsSQL. All that is accomplish is changing the question asked. "The data directory you have specified (C:\PgData) contains a database from an older version of PostgreSQL (8.2) that this version (8.3.6) cannot access. Would you like to use a new data directory C:\PgData-8.3, leaving the old one untouched? Note that PostgreSQL will not automatically convert your data. You REALLY should read the upgrading documentation before continuing. [clean install to new data directory][cancel installation]" "PostgreSQL has detected that another program, probably an older version of PostgreSQL, is listening on port 5432. If you want to use this version on the default port 5432, you will need to stop or uninstall the other program first. [Change PostgreSQL port][Cancel installation]" I agree more verbose install messages on errors and warnings would be nice. Of course, if Windows development is un-fun, windows program installation and installer building is more so. That is very true -- Craig Ringer |
