On 29 March 2011 21:51, Adrian Klaver <adrian.klaver@gmail.com> wrote:
> On 03/29/2011 01:32 PM, Thom Brown wrote:
>>
>> On 29 March 2011 21:28, hubert depesz lubaczewski<depesz@depesz.com>
>> wrote:
>>>
>>> On Tue, Mar 29, 2011 at 07:44:51PM +0100, Thom Brown wrote:
>>>>
>>>> So, I'm overlooking something. Could someone tell me what it is? I
>>>> bet it's something obvious. I'm using 9.1dev if it's relevant.
>>>
>>> perhaps meow is superuser?
>>
>> stuff=> \dg+
>> List of roles
>> Role name | Attributes | Member
>> of | Description
>>
>> -----------+------------------------------------------------+-----------+-------------
>> meow | | {} |
>> testrole | Cannot login | {} |
>> thom | Superuser, Create role, Create DB, Replication | {} |
>>
>
> My guess is you have pg_hba.conf set up to use trust for the connection. In
> your original example testrole failed because it is not a login role not for
> permissions reasons. When \c to stuff as meow can you do \d?
I can do \d, but it doesn't show anything since there's nothing in
there. But it does let me create a table, then see it using \d...
stuff=> \c stuff meow
You are now connected to database "stuff" as user "meow".
stuff=> \d
No relations found.
stuff=> create table test (id serial);
NOTICE: CREATE TABLE will create implicit sequence "test_id_seq" for
serial column "test.id"
CREATE TABLE
stuff=> \d
List of relations
Schema | Name | Type | Owner
--------+-------------+----------+-------
public | test | table | meow
public | test_id_seq | sequence | meow
(2 rows)
--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
