Re: Commands history with psql in a Windows command line shell

Lmhelp1 <lmhelp1@xxxxxxxxx> · Tue, 2 Aug 2016 18:19:33 +0200



    Thank you for your answer.

      
      1.

      Like I wrote in my first post, the command I use to
        launch "psql" is:

      cmd.exe> psql -p <tcp_port> -U <username>
        <database_name>

      So, I do not specify the "--no-readline" option.

      
      2.

      cmd.exe psql <database_name># \s

      history is not supported by this installation

      
      Powershell psql <database_name># \s

        history is not supported by this installation

        
        To install PostgreSQL, I used the
        "postgresql-9.5.2-1-windows-x64.exe" installer the 2016/04/21. 

        So I don't remember much about what I did that day.

        
        3.

        When I do:

      psql <database_name># \set

      HISTFILE does not appear in the result.

      So, I guess it is not set.

      
      Best regards,

      --

      Léa Massiot

      
    On 2016-08-02 5:56 PM, Melvin
        Davidson wrote:

      
        Thank you, Based on 

          https://www.postgresql.org/docs/9.5/static/app-psql.html#APP-PSQL-ENVIRONMENT

          
        The following may be pertinent.

          
          If -n / --no-readline was specified, then command
            history is not used.

          
          What happens if you issue the \s command in psql? Is
            history supported?

          
          What is the value for HISTFILE?

          
          -- 

          
            Melvin Davidson

              I reserve the right to
                    fantasize.  Whether or not you 

                  wish to share my
                    fantasy is entirely up to you. 

              
      On Tue, Aug 2, 2016 at 11:40 AM, David G. Johnston <david.g.johnston@xxxxxxxxx>
      wrote:

    
        On Tue, Aug 2, 2016 at 11:31 AM, Melvin Davidson <melvin6925@xxxxxxxxx> wrote:

        
            Are you doing this in PostgreSQL 7.3 and Windows XP?
              Can you provide us with a little more useful information
              like current PostgreSQL version and O/S?

            
            Otherwise we have absolutely no idea what the problem might
            be.

          
      "Windows (8.1)" refers to the O/S version.
      

      Knowing the PostgreSQL version probably won't make a
        difference though knowing how it was installed might (though not
        for me personally).
    
    
    David J.

      
    On 2016-08-02 5:40 PM, Lmhelp1
        wrote:

      
      Thank you for your answer.

         
         cmd.exe> psql --version

         psql (PostgreSQL) 9.5.2

         
         Like I wrote, the Windows OS is 8.1 Pro.
      Best regards,

         --

         Léa Massiot

         
      On 2016-08-02 5:31 PM, Melvin
          Davidson wrote:

         
          Are you doing this in PostgreSQL 7.3 and Windows XP?
              Can you provide us with a little more useful information
              like current PostgreSQL version and O/S?

             
           Otherwise we have absolutely no idea what the problem
            might be.

           
          On Tue, Aug 2, 2016 at 11:18 AM,
              Lmhelp1 <lmhelp1@xxxxxxxxx>
              wrote:

            
            Hello,

               
               I am using "psql" in "cmd.exe" in Windows (8.1).

               
               Below is the command I use to connect to a
                database with "psql":

               cmd.exe> psql -p <tcp_port> -U
                <username> <database_name>

               
               My problem is the following.

               Suppose I enter one command:

               <database_name># SELECT * FROM
                <a_table_1>;

               and then another one:

               <database_name># SELECT * FROM
                <a_table_2>;

               The commands history "is not working": meaning I
                cannot retrieve these last two commands I entered by
                hitting the top arrow key.

               Instead, I have to type them again.

               
               To try to solve the problem, I entered the
                command:

               <database_name># \set HISTSIZE 100

               but it didn't change anything.

               
               Yesterday, I don't remember what I did, but I
                could access the commands history using Powershell,
                maybe the command "\set HISTSIZE 100" and maybe a
                "psqlrc" file.

               But whatever I've been trying to do since, I
                can't make it work again.

               
               Can you please advise me what to do to make this
                work?

               
               Best regards.

               --

               Léa Massiot

                    
                    -- 

                    Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)

                    To make changes to your subscription:

                    http://www.postgresql.org/mailpref/pgsql-general

                  
           -- 

          
            Melvin Davidson

               I reserve the right to
                    fantasize.  Whether or not you 

                  wish to share my
                    fantasy is entirely up to you.