You seem to be confused by bash's parameter expansion. Better read the
bash manual or a tutorial on that. Or you could open a psql session and
type the commands on the psql prompt to avoid interaction with bash.
suresh adapa wrote:
> Hi,
>
> I am trying to find out limitation on what symbols can be used in
> password option.
>
> Example below attempts fail.
>
> Does not allow to alter password if it starts with '!'
> -----------------------------------------------------
> -bash-3.2$ psql -Upostgres -q -c "alter user gopal with password '!123'"
> -bash: !123: event not found
>
> Allows us to alter password, but fails while authentication.
> ------------------------------------------------------------
> -bash-3.2$ psql -Upostgres -q -c "alter user gopal with password '$123'"
> -bash-3.2$ psql -h 127.0.0.1 -U gopal -d TEST3
> Password for user gopal:
> psql: FATAL: password authentication failed for user "gopal"
> -bash-3.2$ psql -Upostgres -q -c "alter user gopal with password '$abc'"
> -bash-3.2$ psql -h 127.0.0.1 -U gopal -d TEST3
> Password for user gopal:
> psql: FATAL: password authentication failed for user "gopal"
>
> If we use/script tries to use environment variables like $PWD or $PATH.
> It basically expands the ENV variable and its value is stored.
> ----------------------------------------------------------------------
>
> -bash-3.2$ psql -Upostgres -q -c "alter user gopal with password '$PWD'"
>
> -bash-3.2$ psql -h 127.0.0.1 -U gopal -d TEST3
> Password for user gopal:$PWD
> psql: FATAL: password authentication failed for user "gopal"
>
> -bash-3.2$ psql -h 127.0.0.1 -U gopal -d TEST3
> Password for user gopal:/var/lib/pgsql
> Welcome to psql 8.3.6, the PostgreSQL interactive terminal.
>
> Thanks
> SureshA
>
>
> -----Original Message-----
> From: Heikki Linnakangas [mailto:heikki.linnakangas@enterprisedb.com]
> Sent: Wednesday, November 11, 2009 2:46 PM
> To: suresh adapa
> Cc: pgsql-bugs@postgresql.org
> Subject: Re: FW: [BUGS] postgresql-8.3.6-1PGDG : password
>
> suresh adapa wrote:
>> I am basically testing few things as below for one off my Task
>> requirement.
>> Can you please check below Test Case 4,6 and 7 and comment.
>
> I don't understand what you were trying to do and if you think there's
> something wrong there..
>
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com