From: | michael mccafferty <mikemcc(at)darkandbrooding(dot)com> |
---|---|
To: | "carlosinfl (dot)" <carlos(dot)mennens(at)gmail(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Postgres User Home ENV Help |
Date: | 2013-06-20 23:18:34 |
Message-ID: | CALvQigvJUdQvRMrp_1gfEdWx_CmeeE7CmM619U7x=95mVDR0Uw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
I think you are trying to solve the wrong problem.
You should not be switching to user 'postgres' regularly enough that the
default bash shell bothers you. Instead, you should switch to user
'postgres' only when you need superuser access to create new roles,
permissions, databases, etc.
If you create a role that match your normal login, then you can run 'psql'
from your normal account, and you won't need to customize user postgres'
shell environment.
My two cents,
and my best regards,
Mike M
On Thu, Jun 20, 2013 at 2:13 PM, carlosinfl . <carlos(dot)mennens(at)gmail(dot)com>wrote:
> Can someone please help me set the 'postgres' users home ENV so that I
> can simply type 'psql' rather than the rull path and bash doesn't say
> '-bash-4.1$'?
>
> -bash-4.1$ whoami;ls -l;pwd
> postgres
>
> total 12
> drwx------ 2 postgres postgres 4096 Apr 4 18:33 backups
> drwx------ 15 postgres postgres 4096 Jun 18 20:52 data
> -rw------- 1 postgres postgres 1493 Jun 14 21:11 pgstartup.log
>
> /var/lib/pgsql9
>
> --
> Carlos Mennens
>
>
> --
> Sent via pgsql-novice mailing list (pgsql-novice(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-novice
>
From | Date | Subject | |
---|---|---|---|
Next Message | Basil Bourque | 2013-06-21 06:44:47 | Re: Composite Unique Key - Doubt |
Previous Message | carlosinfl . | 2013-06-20 21:13:15 | Postgres User Home ENV Help |