Thank you for this note.
Best regards,
--
Léa Massiot
On 2016-08-02 6:57 PM, Tom Lane wrote:
Lmhelp1 writes:
cmd.exe psql # \s
history is not supported by this installation
This means you have a copy of psql.exe that was built without the readline
library, so history doesn't work either. I'
Lmhelp1 writes:
> cmd.exe psql # \s
> history is not supported by this installation
This means you have a copy of psql.exe that was built without the readline
library, so history doesn't work either. I'm not sure what the state of
the readline library is for Windows; there may not be any version
Thank you for your answer.
I can't see any difference.
In "Properties", there is an entry "Command History" with two fields
"Buffer size" set to 50 and "Number of Buffers" set to 4.
These settings are exactly the same in "cmd.exe" and "SQL Shell"...
Best regards,
--
Léa Massiot
On 2016-08-0
On 08/02/2016 09:39 AM, Lmhelp1 wrote:
Thank you for your answer.
With the "SQL Shell" tool, the commands history is indeed available!
So, I guess I am now going to use this tool instead of "cmd.exe".
This solves my problem.
Or look at the properties of the menu item and see what is done to
e
Thank you for your answer.
With the "SQL Shell" tool, the commands history is indeed available!
So, I guess I am now going to use this tool instead of "cmd.exe".
This solves my problem.
Thank you and best regards.
--
Léa Massiot
On 2016-08-02 6:27 PM, Adrian Klaver wrote:
What happens if yo
On 08/02/2016 09:19 AM, Lmhelp1 wrote:
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 -U
So, I do not specify the "--no-readline" option.
2.
cmd.exe psql # \s
history is not supported by this installation
Powershell psql
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 -U
So, I do not specify the "--no-readline" option.
2.
cmd.exe psql # \s
history is not supported by this installation
Powershell psql # \s
history is not supported by this in
On Tue, Aug 2, 2016 at 11:40 AM, David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Tue, Aug 2, 2016 at 11:31 AM, 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
On Tue, Aug 2, 2016 at 11:31 AM, 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.
>
>
"Windows (8.1)
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 inf
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 wrote:
> Hello,
>
> I am using "psql" in
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 -U
My problem is the following.
Suppose I enter one command:
# SELECT * FROM ;
and then another one:
# SELECT * FROM ;
The commands history "is not workin
12 matches
Mail list logo
