| From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
|---|---|
| To: | "Petri Jooste" <RKWJPJ(at)puknet(dot)puk(dot)ac(dot)za>, <pgadmin-support(at)postgresql(dot)org> |
| Subject: | Re: Error number 35603 Invalid key |
| Date: | 2002-10-23 07:17:39 |
| Message-ID: | 03AF4E498C591348A42FC93DEA9661B8128B15@mail.vale-housing.co.uk |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
> -----Original Message-----
> From: Petri Jooste [mailto:RKWJPJ(at)puknet(dot)puk(dot)ac(dot)za]
> Sent: 23 October 2002 08:05
> To: pgadmin-support(at)postgresql(dot)org
> Subject: Re: [pgadmin-support] Error number 35603 Invalid key
>
>
> Thanks for the reply.
> I tried to recreate the error but cannot at the moment
> because the linux machine with the postgres server is not
> available. Then I tried to recreate the error using postgres
> on cygwin and now I do not get the error. My first guess is
> that it has something to do with permissions, because now (on
> cygwin) the Table form of pgAdmin get its "owner" field
> automatically filled with my username.
> The linux-based postgres has been set up to use md5
> authentication. Could that be the problem ?
Shouldn't be if you can login. On the Linux box, (when it's back up),
will it let you execute the query:
SELECT * FROM pg_user
Thinking about it, if the create table dialogue doesn't list all the
users on the system (because you can read them) then it might well have
trouble. I would be surprised that you weren't getting an error earlier
though.
Anyway, hopefully the logs will tell when the Linux box is available
again.
Regards, Dave.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Houska | 2002-10-23 07:24:05 | |
| Previous Message | Petri Jooste | 2002-10-23 07:05:09 | Re: Error number 35603 Invalid key |