From: | saurabh shelar <saurabhshelar5(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Issue with psqlrc with command line. |
Date: | 2018-08-30 07:37:29 |
Message-ID: | CALBKi8Y4pkKTnDedSWz9-RrjYVb8-hWA=ToGK_MP9HAqo54OQQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi David,
Got your point.
Thank you for the help.
On Wed, Aug 29, 2018 at 9:07 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Wed, Aug 29, 2018 at 8:31 AM, saurabh shelar <saurabhshelar5(at)gmail(dot)com>
> wrote:
>
>> Hi David,
>>
>> Thank you for the help.
>>
>> I was just got confused with the below line mentioned in the document.
>> However, it seems it is still the same behaviour *(i.e --no-psqlrc)*.
>>
>> *"Before PostgreSQL 9.6, the -c option implied -X (--no-psqlrc); this is
>> no longer the case."*
>>
>
> Whether psqlrc is being processed or not is immaterial to the behavior you
> are seeing because -c will not resolve the variable reference prior to
> sending the command to the server.
>
> If you have other non-variable definitions in psqlrc that could affect the
> -c command (or its output - like \pset instructions) those will now be
> applied before sending the command whereas before they would not be.
>
> (admittedly I'm not reading the source code nor have experimented to draw
> this conclusion)
>
> David J.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | a | 2018-08-30 09:13:54 | Ways to deal with large amount of columns; |
Previous Message | Dave Peticolas | 2018-08-30 03:19:07 | Re: WAL replay issue from 9.6.8 to 9.6.10 |