> >
> 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.
[snip]
> The only thing i think that would make sense, is to have the installer
> add exceptions to the windows firewall for thePostgresql ports.
You have a good point.
> 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.
Yuck. Very good point, actually.
I guess sometimes there's no good substitute for having a clue.
Additionally, the more I think about it the more I realise the installer
isn't the right place to tackle some of the issues that _do_ come up.
Windows users seem to be very confused by a service failing to start and
don't seem to know that the OS records information in the event log or
that Pg has its own logs. It'd be nice if the event log messagess
contained a note telling the user where the Pg logs were, and if Pg
could use the messaging service to notify the user of issues like bad
data dir permissions ... but that won't help if the user doesn't know to
look in the event log.
Of course, if you try to start a service and it fails, the generic error
message from Windows tells you to look in the event log for more
information. This may be a case of people who don't _want_ to look into
it and don't want to think about it.
--
Craig Ringer
