From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: Recursive SELECT problem |
Date: | 2006-05-17 14:10:02 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E40138826D@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: 17 May 2006 15:07
> To: Dave Page
> Cc: pgsql-sql(at)postgresql(dot)org
> Subject: Re: [SQL] Recursive SELECT problem
>
> "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> writes:
> > I'm trying to write a query to determine whether or not the current
> > login role has CREATEDB (or CREATEROLE) privileges, either
> directly or
> > inherited from a parent role.
>
> Those privileges don't inherit, so I'm not sure why you need
> a recursive check.
Because I didn't realise they didn't inherit 'cos I missed the note at
the bottom of the CREATE ROLE page :-)
Thanks - that makes life significantly easier!
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-05-17 14:12:52 | Re: Table constraints and INSERT |
Previous Message | Tom Lane | 2006-05-17 14:06:42 | Re: Recursive SELECT problem |