From: | Abhra Kar <abhra(dot)kar(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: postgres connection with port option in shell script |
Date: | 2018-02-17 15:15:36 |
Message-ID: | CAFNULEc_rThO60Mt_g86mE2y6-NVhdw=HE9G2ynR1_jokxMyXw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Feb 14, 2018 at 9:03 PM, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Wed, Feb 14, 2018 at 8:21 AM, Abhra Kar <abhra(dot)kar(at)gmail(dot)com> wrote:
>
>> Hi,
>>
>> I want to get postgres connection in script file. I am executing
>> below command and successfully getting connected ---
>>
>>
>> psql postgresql://$USER:$PASSWORD(at)$HOST/$DATABASE <<END
>>
>>
>>
> If all you are going to do is substitute environment variables into a URI
> why not just identify the environment variables that psql uses directly,
> set those, and call "psql" directly.
>
> select * from abc;
>>
>>
>> This is executing with default 5432 port.If postgres is installed to any
>> other port then port option need to be include here[Don't want to take port
>> from .pgpass file].
>>
>
> You couldn't even if you wanted to. Did you maybe mean the
> .pg_service.conf file?
>
> You should strongly consider using .pgpass instead of "$PASSWORD" -
> especially depending upon where perform the export.
>
>
>> How I can modify this command with PORT option.
>>
>
> https://www.postgresql.org/docs/10/static/libpq-connect.
> html#LIBPQ-CONNSTRING
>
> David J.
>
Hi David,
I meant .pgpass file with in user home directory.And I
followed the link you provided.It worked.Thanks a lot.
Regards,
Abhra
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-02-17 16:26:12 | Re: Any hope for more specific error message for "value too long..."? |
Previous Message | hmidi slim | 2018-02-17 10:08:39 | Join query |