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
ful 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 <mailto:lmhe...@orange.fr>> wrote:
Hello,
I am using "psql" in "cmd.exe" in Windows (8.1).
ly 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 y
e:
What happens if you use the SQL Shell from the program menu on the
Start Menu?:
http://www.enterprisedb.com/resources-community/tutorials-quickstarts/windows/getting-started-postgres-plus-tutorial-windows
On 2016-08-02 6:19 PM, Lmhelp1 wrote:
Thank you for your answer.
1.
Like I wr
ot;SQL Shell"...
Best regards,
--
Léa Massiot
On 2016-08-02 6:39 PM, Adrian Klaver wrote:
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
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 e
