Message-ID: <cac32bd7-f620-465d-8e1a-0300cfb2c321@postgresfriends.org>
Date: Tue, 26 Dec 2023 22:45:31 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: A tiny improvement of psql
To: Tom Lane <tgl@sss.pgh.pa.us>, Kevin Wang <kevinpgcloud@gmail.com>
Cc: pgsql-hackers@postgresql.org
References: <CAAZWVYpquc=nHUAnmSS62SYS0wQe8SNNr_X6H-=ba9i5BWJOjA@mail.gmail.com>
 <2036813.1703608601@sss.pgh.pa.us>
Content-Language: en-US
From: Vik Fearing <vik@postgresfriends.org>
In-Reply-To: <2036813.1703608601@sss.pgh.pa.us>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/cac32bd7-f620-465d-8e1a-0300cfb2c321%40postgresfriends.org>
Precedence: bulk

On 12/26/23 17:36, Tom Lane wrote:
> Kevin Wang <kevinpgcloud@gmail.com> writes:
>> As you know, we can use the UP arrow key to get the previous command to
>> avoid extra typing. This is a wonderful feature to save the lives of every
>> DBA. However, if I type the commands like this sequence: A, B, B, B, B, B,
>> B,  as you can see, B is the last command I execute.
> 
>> But if I try to get command A, I have to press the UP key 7 times.  I think
>> the best way is: when you press the UP key, plsql should show the command
>> that is different from the previous command, so the recall sequence should
>> be B -> A, not B -> B -> ... -> A.  Then I only press the UP key 2 times to
>> get command A.
> 
> This is driven by libreadline, not anything we control.  I have
> seen the behavior you describe in some other programs, so I wonder
> whether it's configurable.

It is kind of something we control.  Per the psql docs, setting

     HISTCONTROL=ignoredups

will do the trick.

https://www.postgresql.org/docs/current/app-psql.html#APP-PSQL-VARIABLES-HISTCONTROL
-- 
Vik Fearing