Re: FAQ_MSWIN patch: clarify instructions - Mailing list pgsql-cygwin

From Jason Tishler
Subject Re: FAQ_MSWIN patch: clarify instructions
Date
Msg-id 20031201154909.GE1040@tishler.net
Whole thread Raw
In response to FAQ_MSWIN patch: clarify instructions  (Daniel Convissor <danielc@analysisandsolutions.com>)
Responses Re: FAQ_MSWIN patch: clarify instructions  (Daniel Convissor <danielc@analysisandsolutions.com>)
List pgsql-cygwin
On Fri, Nov 28, 2003 at 03:34:46PM -0500, Bruce Momjian wrote:
> Should any part of this patch be applied?

IMO, no.  See below...

On Thu, Nov 27, 2003 at 01:13:34AM -0500, Daniel Convissor wrote:
> -    3c.  Start up the postmaster.  Use a command similar to the
> -         following:
> +         You must be logged on as the user that installed Cygwin in
> +         order for this command to work.

The above is not true if your Cygwin environment is set up correctly.
Unfortunately, a change in Windows security and a deficiency in Cygwin's
setup.exe exacerbates this problem.

> +         When referring to paths outside of Cygwin's root, PostgreSQL
> +         expects the paths to use the "/cygdrive/<drive>/<dir>" syntax
> +         rather than the Windows like syntax of "<drive>:/<dir>."
> +         Example:
> +
> +            /cygdrive/d/pgsql/data
> +

IMO, the above is extraneous detail.

> -            postmaster -D /usr/local/pgsql/data
> +    3c.  Set the PGDATA environment variable.  Example commands would be:
> +
> +            PGDATA=/usr/local/pgsql/data
> +            export PGDATA
> +
> +    3d.  Start up the server:
> +
> +            pg_ctl start

IMO, the above is only a "style" change.

>           This will start the postmaster, and if successful you will
>           see some initial log entries, and an entry "LOG: database
> @@ -58,6 +72,38 @@
>      refer to the README document included with Cygwin PostgreSQL.  It
>      is installed in the /usr/share/doc/Cygwin directory.
>
> +6.  If you don't want to run the programs as a service, the following
> +    steps are helpful:
> +
> +    6a.  Add the following lines to the .profile file in your home
> +         directory.  This will make it easier to start the server when
> +         desired.  Of course, adjust the paths as needed:
> +
> +            ipc-daemon2 &

IMO, starting ipc-daemon2 from a user's .profile is a bad approach to
achieve this goal.  Use the service approach or Windows startup folder
instead.

> +            PGDATA=/usr/local/pgsql/data
> +            export PGDATA
> +
> +    6b.  To start the server, use this command:
> +
> +            pg_ctl start
> +
> +    6c.  Before exiting your Cygwin shell prompt, make sure to stop
> +         the PostgreSQL server using the following command:
> +
> +            pg_ctl stop

IMO, the above is a rehash of information already in the FAQ.

> +         This procedure can be automated by putting that command inside
> +         the .bash_logout file in your home directory.  You will need to
> +         create that file if it does not yet exist.

IMO, the above is extraneous detail.

> +7.  If you want other users to be able to run PostgreSQL, it is
> +    necessary to ease the permissions on some files.  Adjust the
> +    permissions and paths to suit your requirements.
> +
> +       chmod 755 /usr/bin/pg_* /usr/bin/postgr*
> +       chmod 666 /usr/local/pgsql/data/global/pg_pwd
> +       chmod 666 /usr/local/pgsql/data/global/pg_fsm.cache
> +

IMO, the above is a bad approach to achieve this goal.  Use the service
approach instead.

Jason

--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D  8784 1AFD E4CC ECF4 8EF6

pgsql-cygwin by date:

Previous
From: Jason Tishler
Date:
Subject: Re: initdb failed: invalid value for parameter "lc_messages": "ENU"
Next
From: Jason Tishler
Date:
Subject: Re: install problems with ipc-daemon2