This is the mail archive of the
mailing list for the Cygwin project.
Re: Best practice for running pgsql under cygwin?
- From: Ryan Johnson <ryan dot johnson at cs dot utoronto dot ca>
- To: Andrey Repin <cygwin at cygwin dot com>
- Cc: Andrey Repin <anrdaemon at freemail dot ru>
- Date: Sat, 22 Dec 2012 09:18:23 -0700
- Subject: Re: Best practice for running pgsql under cygwin?
- References: <50D4A8C6.email@example.com> <firstname.lastname@example.org>
On 22/12/2012 7:36 AM, Andrey Repin wrote:
Greetings, Ryan Johnson!Most student work will be done on private installs of pgsql, which they
can set up however they'd like.
I'm trying to set up pgsql for classroom instruction, which means I need
to allow students to connect to my machine, preferably with no OS-level
privileges and minimal database privileges.
If your class is about setting up the server, you should really use virtual
If it's about using SQL on already running server, it makes no difference, if
you've your server as Cygwin port or native application - clients will never
It is unclear to me, why you need to let students access the machine.
Setting up the database roles looks straightforward enough, but I'm having
trouble figuring out how to secure the machine.
However, we're going to do classroom demos at times, including one where
we have fun with different isolation levels; I'll need multiple students
logged into the same database so they can mess with each others'
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple