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 databas
I would like to create multiple databases, each with its own disk location.
I have followed the instructions in the Administrator's Guide and have a
couple of questions.
1. Since the pg_ctl -D option only appears to take a single location, should
this be set to the location of the template1 da
"Tauren Mills" <[EMAIL PROTECTED]> writes:
> 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.
If you get a response about "y
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.
So
I'm new to PostgreSQL and am trying to implement it in a shared web
application hosting environment. Ideally, I'd like each customer to have
their databases stored within their own user area. For instance, the
/home/user1/.pgsql would contain all of user1's databases.
It looks like this could b
"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
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 a
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 r
I've sent this to both pgsql-general and pgsql-admin. Please advise which
is the proper list for this type of question.
I'm new to PostgreSQL and am trying to implement it in a shared web
application hosting environment. Ideally, I'd like each customer to have
their databases stored within thei
