Re: [ADMIN] Alternate database locations

2002-04-17 Thread Tom Lane
Charlie Toohey [EMAIL PROTECTED] writes: 1. Since the pg_ctl -D option only appears to take a single location, should this be set to the location of the template1 database created as part of the Postgres installation, or, do I have to somehow specify the location of each of my databases in

RE: [ADMIN] Alternate database locations

2001-06-05 Thread Tauren Mills
I'm not sure how this message got posted again. I think it is because I posted it to the newsgroup first but it was rejected since I was not a member of the list. Now that I'm a member, I'm assuming it went through. However, I'd already sent it directly to the list as an email after joining.

Re: [ADMIN] Alternate database locations

2001-06-04 Thread Tom Lane
Peter Eisentraut [EMAIL PROTECTED] writes: However, this page indicates that there are security risks in doing this. What are those risks? If I prevent users other than the superuser postgres from being able to create and drop databases, are there any security risks? No. The risks are

RE: [ADMIN] Alternate database locations

2001-06-04 Thread Tauren Mills
Thanks for the feedback! However, this page indicates that there are security risks in doing this. What are those risks? If I prevent users other than the superuser postgres from being able to create and drop databases, are there any security risks? No. The risks are related to the

Re: [ADMIN] Alternate database locations

2001-06-04 Thread Tom Lane
Tauren Mills [EMAIL PROTECTED] writes: Is there any way to keep each customer's database within their user area without the chance of breaking the database server? If you want completely decoupled service for each user, then give each of them their own independent installation, running as