Re: UPDATE01: Unable to run createlang (or psql for that matter) - Mailing list pgsql-general

From John Gage
Subject Re: UPDATE01: Unable to run createlang (or psql for that matter)
Date
Msg-id DF0F2000-4A26-4B7B-84C1-A2605B8DD7CC@numericable.fr
Whole thread Raw
In response to Unable to run createlang (or psql for that matter)  (John Gage <jsmgage@numericable.fr>)
List pgsql-general
I have made some progress by looking at the documentation and at how
Mac OSX sets up privileges.

If I su to root and then su to postgres, I can access createlang and
psql (although my user $PATH seems to be inoperative).

What I can't do is su from me as user (not root) to postgres.  I get
asked for a password that is not any password that exists.  For
example, it is not the password that postgres uses to get to the
databases.

I am now going to see if I can find the mystery password for postgres.


On Apr 25, 2010, at 11:08 AM, John Gage wrote:

> If I open a bash terminal and type createlang -l, I get:
>
> JohnGage:~ johngage$ createlang -l
> -bash: createlang: command not found
> JohnGage:~ johngage$ psql
> -bash: psql: command not found
>
> as one can see, the same thing happens with psql.
>
> The way I have been using psql is by pulling down the plugins menu
> in pgAdmin3 and selecting (the only selection) psql.
>
> My $PATH variable includes the path to both createlang and psql.
>
> What am I doing wrong?
>
> John
>
>
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general


pgsql-general by date:

Previous
From: Oliver Kohll - Mailing Lists
Date:
Subject: Re: Invalid objects
Next
From: John Gage
Date:
Subject: Re: UPDATE02Unable to run createlang (or psql for that matter)