Previous command not accessible in postgres 17 beta

Lists: pgsql-bugs
From: usman khan <usman(dot)khan9805(at)gmail(dot)com>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Previous command not accessible in postgres 17 beta
Date: 2024-06-13 05:30:01
Message-ID: CA+GTGZF=fnO+_50tsuty740SLPzeo=tD4ZGVjzhso_oHBZBr0w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs

Dear Concerned,
I wanted to let you know that I am running postgres 17 in rocky linux and
when I tries to fetch previous command by pressing up arrow key than
instead of fetching previous key, I am getting following values:
^[[A^[[A^[[B^[[A
Please look into this.

Thank You


From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: usman khan <usman(dot)khan9805(at)gmail(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Previous command not accessible in postgres 17 beta
Date: 2024-06-13 14:33:42
Message-ID: 1794494.1718289222@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs

usman khan <usman(dot)khan9805(at)gmail(dot)com> writes:
> I wanted to let you know that I am running postgres 17 in rocky linux and
> when I tries to fetch previous command by pressing up arrow key than
> instead of fetching previous key, I am getting following values:
> ^[[A^[[A^[[B^[[A

Nothing around that has changed in Postgres. The likely cause is
either that your new psql was built without readline support, or
that you have the wrong TERM setting so that what your keyboard
emits for up-arrow is not what readline is expecting.

regards, tom lane


From: "Wetmore, Matthew (CTR)" <Matthew(dot)Wetmore(at)evernorth(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, usman khan <usman(dot)khan9805(at)gmail(dot)com>
Cc: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: RE: [EXTERNAL] Re: Previous command not accessible in postgres 17 beta
Date: 2024-06-13 15:08:34
Message-ID: PH0PR12MB54998A3DE9ABBD7FA0D50999F5C12@PH0PR12MB5499.namprd12.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs

I had a new ubuntu install (JJ) and when I installed from source, I hit Readline error in with GCC.

I had to manually download libReadline-dev (or whatever it's exact name is)

not sure if it was mysetup, or Ubuntu or Source.

so if everything installed, Readline is probably OK.

I would look at Tom's second advice with TERM.

-----Original Message-----
From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Sent: Thursday, June 13, 2024 7:34 AM
To: usman khan <usman(dot)khan9805(at)gmail(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: [EXTERNAL] Re: Previous command not accessible in postgres 17 beta

usman khan <usman(dot)khan9805(at)gmail(dot)com> writes:
> I wanted to let you know that I am running postgres 17 in rocky linux
> and when I tries to fetch previous command by pressing up arrow key
> than instead of fetching previous key, I am getting following values:
> ^[[A^[[A^[[B^[[A

Nothing around that has changed in Postgres. The likely cause is either that your new psql was built without readline support, or that you have the wrong TERM setting so that what your keyboard emits for up-arrow is not what readline is expecting.

regards, tom lane

----------------------------------------------------------------------
CONFIDENTIALITY NOTICE: If you have received this email in error, please immediately notify the sender by e-mail at the address shown. This email transmission may contain confidential information. This information is intended only for the use of the individual(s) or entity to whom it is intended even if addressed incorrectly. Please delete it from your files if you are not the intended recipient. Thank you for your compliance. Copyright (c) 2024 Evernorth


From: usman khan <usman(dot)khan9805(at)gmail(dot)com>
To: "Wetmore, Matthew (CTR)" <Matthew(dot)Wetmore(at)evernorth(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: [EXTERNAL] Re: Previous command not accessible in postgres 17 beta
Date: 2024-06-14 05:45:54
Message-ID: CA+GTGZFmxUEgczaudvj1rBSemSw7DhGoeTQf9ZQ3g4UviSV-xw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs

Hello,
Thank you for the response. It is solved now using readline library

On Thu, Jun 13, 2024 at 8:08 PM Wetmore, Matthew (CTR) <
Matthew(dot)Wetmore(at)evernorth(dot)com> wrote:

> I had a new ubuntu install (JJ) and when I installed from source, I hit
> Readline error in with GCC.
>
> I had to manually download libReadline-dev (or whatever it's exact name is)
>
> not sure if it was mysetup, or Ubuntu or Source.
>
> so if everything installed, Readline is probably OK.
>
> I would look at Tom's second advice with TERM.
>
> -----Original Message-----
> From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> Sent: Thursday, June 13, 2024 7:34 AM
> To: usman khan <usman(dot)khan9805(at)gmail(dot)com>
> Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
> Subject: [EXTERNAL] Re: Previous command not accessible in postgres 17 beta
>
> usman khan <usman(dot)khan9805(at)gmail(dot)com> writes:
> > I wanted to let you know that I am running postgres 17 in rocky linux
> > and when I tries to fetch previous command by pressing up arrow key
> > than instead of fetching previous key, I am getting following values:
> > ^[[A^[[A^[[B^[[A
>
> Nothing around that has changed in Postgres. The likely cause is either
> that your new psql was built without readline support, or that you have the
> wrong TERM setting so that what your keyboard emits for up-arrow is not
> what readline is expecting.
>
> regards, tom lane
>
>
> ----------------------------------------------------------------------
> CONFIDENTIALITY NOTICE: If you have received this email in error, please
> immediately notify the sender by e-mail at the address shown. This email
> transmission may contain confidential information. This information is
> intended only for the use of the individual(s) or entity to whom it is
> intended even if addressed incorrectly. Please delete it from your files
> if you are not the intended recipient. Thank you for your compliance.
> Copyright (c) 2024 Evernorth
>