On 07/02/2013 03:35 AM, Albe Laurenz wrote:
> Michael Orlitzky wrote:
>> I want to be able to create a database, set up the (default) group
>> permissions, and have them work, even when a new user is added to one of
>> the groups. Right now I don't know of a way to get default group
>> permissions.
Michael Orlitzky wrote:
> I want to be able to create a database, set up the (default) group
> permissions, and have them work, even when a new user is added to one of
> the groups. Right now I don't know of a way to get default group
> permissions.
There is none, as far as I can say.
You have tw
On 07/01/2013 10:21 AM, Andrew Sullivan wrote:
>
> So not "can do anything", but can read and write any database. Looks
> to me to be something like
>
>CREATE ROLE adminuser NOSUPERUSER NOCREATEDB NOCREATEROLE
>NOCREATEUSER INHERIT LOGIN NOREPLICATION ADMIN;
>
> Whenever a database is c
On Mon, Jul 01, 2013 at 09:34:24AM -0400, Michael Orlitzky wrote:
> >> # Admins can do anything.
> >
> > You've been able to create this situation with the superuser flag for
> > as long as I can remember (I started with Postgres in the 6.5.x era,
> > but I won't claim my memory goes back that
On 07/01/2013 03:36 AM, Albe Laurenz wrote:
>
> I took a look, but it takes more time than I'm willing to spend
> to actually get to your problem.
>
> Could you outline briefly what the problem is?
>
(I'm going to copy from the README a bit, but I'll try to pare it down)
I want to be able to c
On 06/30/2013 09:56 PM, Andrew Sullivan wrote:
> On Sun, Jun 30, 2013 at 09:31:18PM -0400, Michael Orlitzky wrote:
>> (why do I get the feeling nobody is going to check out the repo):
>
> Probably because you're asking random strangers on the Internet to
> help you solve their problems, and many o
Michael Orlitzky wrote:
> We use Postgres for shared hosting; i.e. what most people use MySQL for.
> The biggest headache for us so far has been that we're unable to get
> group permissions set up effectively so that different groups of
> customers, admins, apaches, etc. can access/modify the data
On Sun, Jun 30, 2013 at 09:31:18PM -0400, Michael Orlitzky wrote:
> (why do I get the feeling nobody is going to check out the repo):
Probably because you're asking random strangers on the Internet to
help you solve their problems, and many of such strangers have other
things to do than go somewhe
On 06/30/2013 09:12 PM, Andrew Sullivan wrote:
>
> If you want "easy", then just give different databases per user. If
> you want complicated, you need an administrator; yes, that needs to be
> in some sense under the control of the host. We have roughly 40 years
> of experience with these thing
On 06/30/2013 08:45 PM, David Johnston wrote:
>
> So PostgreSQL is only useful, for shared hosting, when the only permissible
> access is via vendor-supplied resources (APIs, administrators, etc...)?
>
I'm not sure I understand, but I don't think that's what I'm saying. I
want my customers and c
On 06/30/2013 07:06 PM, John R Pierce wrote:
> On 6/30/2013 12:46 PM, Michael Orlitzky wrote:
>> We use Postgres for shared hosting; i.e. what most people use MySQL for.
>> The biggest headache for us so far has been that we're unable to get
>> group permissions set up effectively so that different
On Sun, Jun 30, 2013 at 05:45:47PM -0700, David Johnston wrote:
> So PostgreSQL is only useful, for shared hosting, when the only permissible
> access is via vendor-supplied resources (APIs, administrators, etc...)?
No, of course not, especially in light of recent improvements. But
any finely-gr
John R Pierce wrote
> On 6/30/2013 12:46 PM, Michael Orlitzky wrote:
>> We use Postgres for shared hosting; i.e. what most people use MySQL for.
>> The biggest headache for us so far has been that we're unable to get
>> group permissions set up effectively so that different groups of
>> customers,
On 6/30/2013 12:46 PM, Michael Orlitzky wrote:
We use Postgres for shared hosting; i.e. what most people use MySQL for.
The biggest headache for us so far has been that we're unable to get
group permissions set up effectively so that different groups of
customers, admins, apaches, etc. can access
We use Postgres for shared hosting; i.e. what most people use MySQL for.
The biggest headache for us so far has been that we're unable to get
group permissions set up effectively so that different groups of
customers, admins, apaches, etc. can access/modify the data they need,
without manual interv
15 matches
Mail list logo
