Команда postgres psql не распознается в среде windows

команда postgres «psql» не распознается в среде windows

кажется, я его настроил, у меня есть моя база данных.yml с помощью postgres, и я могу подключить базу данных с pgadmin III, но когда я попытался с помощью команды psql проверить, какая версия, она говорит, что не распознается? Есть идеи, что мне делать?

Я использую windows и использую командную строку с Ruby on Rails. Использование PostgreSQL 9.2, установленного с помощью установщика EnterpriseDB one-click.

4 ответов

предполагая, что вы установили PostgreSQL в Windows с установщиком PostgreSQL «One-click», упакованным EnterpriseDB, psql не добавляется к PATH автоматически. Это отчасти потому, что добавление его в путь может вызвать путаницу, когда у людей установлено несколько версий PostgreSQL.

или добавить psql для переменные среды, см. например этот руководство.

Открыть Командную Строку

если на строке выше не отображается версия psql, выполните следующие действия

Откройте командную строку и повторите

если есть пробел после ****** ; тогда это не сработает. Вы действительно можете ввести %PATH% в командной строке cmd и посмотреть, как ваша переменная среды и пространство выглядит. Я пробовал оба случая для вас, первый с пространством имел ту же ошибку, о которой Вы упомянули, а второй без пространства работал.

вам нужно установить как bin, так и путь lib в переменной среды PATH, разделенной точкой с запятой:

%PROGRAMFILES\%с PostgreSQL 9.2 ОГРН;%PROGRAMFILES%\с PostgreSQL 9.2Либ

Источник

Setting Windows PATH for Postgres tools

If, after installing PostgreSQL, you face “psql not recognized as an internal or external command” error when you try to run psql from command prompt, then most probably all you need to do to solve this problem is to add the Postgres’s bin directory to the PATH system variable (the PATH is a system variable which allows Windows with the help of the Command prompt or the Terminal window find executables).

In this blog post, we’ll share seven simple steps that describe how to add the folder to the Windows 10 PATH variable.

Step 1. Run Windows Search on your Windows 10 machine by pressing WIN+S. You will see the Search Textbox.

Go to the “Advanced” tab and click on the “Environment Variables” button at the bottom. The “Performance,” “User Profiles,” and “Startup and Recovery” options can also be set in this tab.

Step 4. The “Environment Variables” window will be opened. This is divided into two boxes with User variables and System variables – where all variables and their values are displayed.

Find the “Path” variables in the System variables box, as shown in the screenshot above.

Step 5. Double click on the “Path” variable.

The list with all Path variables will be opened, where the Path variables can be edited, added, and deleted.

Andrew
March 26, 2020 @ 4:31 pm

Thank you!! Exactly what I needed.

Mathew Dunbaugh
April 16, 2020 @ 12:55 am

Awesome. This is the most simple, straightforward answer I could find. Thanks.

Walter Mazvuru
April 22, 2020 @ 5:10 am

Thanks for the heads up! It is the best solution I have seen so far.

Muhammadhusayn Olimjonov
May 7, 2020 @ 3:34 pm

thank you very much! i have been stuck for a long time until I found this. thank you again!

Mercy Kipkoros
June 24, 2020 @ 3:07 am

Thanks a lot for this, I was stuck a whole day on it and you solved my problem in less than 20 min.

Naveen
July 1, 2020 @ 7:32 am

Thanks You 🙂
Very Helpful and Informative 🙂

Lebene
July 3, 2020 @ 2:16 pm

I cannot however just enter psql and go. It is showing my normal C drive user acc as the default e.g. C:UsersMe> and then if I type psql, it asks for my user password which does not work.

What can I do? On postgres 12. Thank you

Jay
July 6, 2020 @ 6:06 pm

Emilia
June 3, 2022 @ 8:00 pm

path
July 19, 2020 @ 9:39 pm

Is this the default system variable in Windows 10? Because I accidentally deleted the value of path, and PATHEXT, and restarted the computer, the computer restore did not open. Now the command window CMD input other commands are not internal or internal commands. What should I do？

Anonymous
August 20, 2020 @ 7:02 pm

Anonymous
October 20, 2020 @ 9:15 am

Daniel McLaren
December 1, 2020 @ 6:58 am

Brilliant, the screenshots really helped. Thanks

Ezrqn Kemboi
January 16, 2022 @ 2:13 am

This works very well.

Esther
February 12, 2022 @ 9:22 pm

Thank you so much, exactly what I need

Anonymous
March 20, 2022 @ 9:52 am

Cornelia
March 30, 2022 @ 12:10 pm

Thanks, first of all! All done, I can see the path on my command line when echo %PATH%, but still if I try to type any command using psql the output is the same : ‘psql’ is not recognized as an internal or external command,
operable program or batch file…..what can I do to solve the issue? Thanks

Alex
April 1, 2022 @ 10:06 am

This issue can happen if:
1. There is no psql.exe utility in the directory that is in the PATH variable
2. The computer hasn’t been restarted after changing the variable

Anonymous
April 5, 2022 @ 1:02 pm

Thank you very much

Jaloliddin Murodullayev
June 22, 2022 @ 10:11 am

Binoj Joseph
June 23, 2022 @ 7:44 pm

Bilbo Bct
July 2, 2022 @ 8:38 am

That was quite helpful. Thanks!!

Cristhian
July 21, 2022 @ 11:02 pm

Nice, it’s working for me

Anonymous
July 24, 2022 @ 12:20 am

Really clearly explained and helpful, thanks.

Anonymous
August 19, 2022 @ 5:20 am

Lyle R.
September 16, 2022 @ 12:03 pm

I’ve had a problem with pythons pg_config not being on a path. I’ve never worked with this PATH and my whole backend development team of mine has been waiting more than a week to get things fixed for ready for production. I’ve looked everywhere for how to do this and this is one of the only hands-down straight-up examples there for this.

Источник

pg:psql might not work on windows? #334

from someone writing into to devcenter feedback

After installing postgresql on windows, I’m unable to run heroku pg:psql. It gives me the message «The local psql command could not be located». I tried adding the path to the PATH environment variable. I’m able to run the command myself (by typing psql), but heroku still can’t find the executable.

The text was updated successfully, but these errors were encountered:

I haven’t heard any further info here (and don’t really have direct access to ask them follow up questions). So I’ll close for now, but keep an eye out.

When this occurred for me the issue was with quotes in the Windows path, so just a local config issue.

Originally I had «C:Program FilesPostgreSQL9.1bin» (with quotes) at the end of PATH. The PSQL command runs, but starts by displaying:
could not find a «psql» to execute

Running «heroku pg:psql DBNAME» failed with the message «The local psql command could not be located».

After resetting PATH to leave out the quote PSQL runs without an error, and heroku pg:psql DBNAME connects to the remote DB.

Hello, I am getting a similar issue, I tried to remove the quotes in the path mentioned by stprior but it didnot solve the issue. Is there any other solution or things I need to check?
Thanks

Thank you stprior, your suggestion worked.

Make sure to restart the command shell after changing the contents of the Windows path. This solved my issue (after adding the Postgresql bin directory to my path).

In Command Prompt write:

set PATH=%PATH%;C:Program FilesPostgreSQL9.2bin

Change the above directory e.g. «C:Program FilesPostgreSQL9.2» to your installed postgresql’s ‘bin’ directory.

Anyone know how to get this working in the Cygwin bash terminal?

Mine still doesn’t work. but it worked on a friend’s computer

Same problem, Windows 8. Added C:Program FilesPostgreSQL9.3bin, didn’t work.
Added «C:Program FilesPostgreSQL9.3bin» Still didn’t work.

! The local psql command could not be located

When I run «heroku pg:psql»

I guess it’s not relevant When I run psql in the Command Line it runs and prompt for a password I don’t know(How can i retrieve it?)..

@yloewidt, were you ever able to solve this issue? I’m running Windows 7 and all my path variables are set up correctly, since I can access psql locally as well as run ‘heroku pg:psql’. pg:ps or pg:push, no luck.

I am also having this problem using Windows 8 and PG 9.3.4. Running psql at command prompt gives me the expected postgres=# prompt. However, running:

Returns «The local psql command could not be located». My PATH seems appropriately set up, and when I run rails console and execute this statement:

I am presented with the postgres prompt. I’m looking through the code to see if I can figure out what is going on because it’s a frustrating problem to have.

What is happening is that dump_restore_cmd in pg_dump_restore.rb returns a string like this:

which is the string that’s called as part of the private run function here

Executing this on Windows raises Errno::ENOENT (because the Windows command line fails to find an executable called «env»), resulting in the error message we’re seeing. I think stripping out or changing the way the environment variables are set will fix this issue. For now, I’m just going to use this to format the statement the way I need it and run pg_dump and pg_restore manually.

@adamscruggs good catch and explanation. I’ve patched it on master here: 6f43cf7

I’ll try to get a release out soon. Part of the confusion above was that the error message looks the same, but has a much different cause (lacking psql in path vs lacking env in path). So hopefully we’ll have this sorted more completely soon.

Remove the quotes fixed my problem.

A reboot fixed it for me. I think because that forces cygwin to update its path.

@will I am on Windows 8.1 with Postgres 9.4 on AMD64. I have Postgres in my PATH, so I no longer get ‘the local psql could not be located’. However, it still does not work for me. Here is my output:

I just read your post on SO http://stackoverflow.com/questions/25870388/heroku-pgpull-failing-to-populate-schema. Surely there are other people on Windows who have successfully uploaded a database to Heroku. How are they doing it? Clearly I can’t stay on Heroku if I can’t use my database.

I just read your post on SO http://stackoverflow.com/questions/25870388/heroku-pgpull-failing-to-populate-schema. Surely there are other people on Windows who have successfully uploaded a database to Heroku. How are they doing it? Clearly I can’t stay on Heroku if I can’t use my database.

Yes, you can upload a database, you just can’t use the heroku command to do it.

you need to look at the full url with heroku config of the database and first use pg_dump to take a dump of your local database, and then PG_PASSWORD=

if you want to restore a local dump to heroku

I could not get Git Bash to accept these commands. It kept saying «pg_dump:
too many command-line arguments (first is «-f»)» Is this a Windows issue?

But uploading to Dropbox and then restoring from there worked, so it is
there without all the flags. Now I have an import error so until that is
resolved I don’t really know what I have for a db. Thx.

On Mon, Mar 16, 2015 at 2:07 PM, Will Leinweber notifications@github.com
wrote:

I just read your post on SO
http://stackoverflow.com/questions/25870388/heroku-pgpull-failing-to-populate-schema.
Surely there are other people on Windows who have successfully uploaded a
database to Heroku. How are they doing it? Clearly I can’t stay on Heroku
if I can’t use my database.
Yes, you can upload a database, you just can’t use the heroku command to
do it.

—
Reply to this email directly or view it on GitHub
#334 (comment).

Источник

psql command not found

PostgreSQL is a very popular database engine used by a lot of websites, is one of the most used relational database management system available, and after installing it we can use some tools that it includes. One of these tools is a command-line tool called psql, and today we are going to learn a lot about it, and how to fix the famous ‘psql command not found’ error on your systems.

About the psql command

So as we said, the psql command is related to the PostgreSQL RDBMS. But what does this command do exactly? Let’s start by explaining that.

psql is a command-line tool that grants us the ability to interact with the PostgreSQL RDBMS using the command line o terminal of our system.

There are different ways to use or interact with an RDBMS. Some of these are graphic programs like phpMyAdmin, which is used for another RDBMS called MySQL (there is a version of it for PostgreSQL too), and there are less graphic ways like the command-line or terminal. But why would someone use a terminal if a nice software with a nice GUI can be used instead?

Well, some people are more used to the terminal, and in some cases the features available in these tools are different, so even if you do have a GUI to interact with an RDBMS you may be lacking a function that is available in the terminal, and vice versa of course.

What can I do with psql?

As we said, it is used to connect with PostgreSQL so we can then issue different queries, and of course, see the results of those queries. It includes a lot of functions, around 30 to be more precise, but some are more important than others so let’s see which of these functions or options are used the most.

How can I fix the psql command not found error on Linux?

So now that we have explained what psql is exactly and how it can be used to interact with PostgreSQL databases let’s see how can we resolve one of the most common problems associated with this tool: the not found error.

If you ever come across the psql command not found error then you may, or may not, be doing something wrong. Before explaining the solution, let’s see what is going on here.

When you get the psql not found error it means that the binary/executable file for psql wasn’t found in your user’s PATH. Depending on how PostgreSQL was installed it may or may not be placed in your PATH.

We can also get this error if we haven’t installed PostgreSQL yet, in which case the solution is to install it of course and check again after that.

But what if PostgreSQL is installed but you still get this error anyway? Well, don’t worry, it’s pretty easy to solve this problem, and this solution works for both CentOS and Ubuntu systems, and for most Linux distros actually.

First, let’s run a very useful command called ‘updatedb’, which nowadays comes included in most distros by default as a part of the ‘locate’ tool. It may run for a few minutes before finishing:

Once it finishes, the locate cache database will be updated and we can use it to find the exact location of the psql command, so let’s run this in our shell:

Once the exact path of the binary is found we only have to create a symlink. For example, if the psql binary was found in the path ‘/usr/lib/postgresql/9.5/bin/psql’ then we only need to issue the following command to create a symlink:

This way the binary will be available in our PATH and we will be able to execute it quickly just by typing “psql” in our shell. This is the easiest and quickest way to solve the psql command not found error.

Summary

So today we have learned a bit more about the psql tool which is used in the shell to issue commands and queries in PostgreSQL, and it can also be used in bash scripts that connect to this RDBMS.

We also know how to fix the psql command not found error, which is one of the most common errors related to this tool. The solution is quite easy and is compatible with most Linux distros, requiring only a symlink to add the binary to the user’s PATH.

Источник

Postgres «psql not recognized as an internal or external command»

For Postgres, I keep getting this error multiple times even though I have already set the location of the bin folder to the path variable in Windows 8. Is there something else I’m missing?

(I can’t post pictures since I don’t have enough reputation)

11 Answers 11

Just an update because I was trying it on Windows 10 you do need to set the path to the following: ;C:Program FilesPostgreSQL9.5bin ;C:Program FilesPostgreSQL9.5lib

You can do that either through the CMD by using set PATH [the path] or from my

computer => properties => advanced system settings=> Environment Variables => System Variables

Then search for path.

Important: don’t replace the PATHs that are already there just add one beside them as follows ;C:Program FilesPostgreSQL9.5bin ;C:Program FilesPostgreSQL9.5lib

Please note: On windows 10, if you follow this: computer => properties => advanced system settings=> Environment Variables => System Variables> select PATH, you actually get the option to add new row. Click Edit, add the /bin and /lib folder locations and save changes.

Important note:

Replace 9.5 with your current version number. As of 2022, that is 13

It could be that your server doesn’t start automatically on windows 10 and you need to start it yourself after setting your Postgresql path using the following command in cmd:

You need to be inside «C:Program FilesPostgreSQL11.4bin» directory to execute the above command.

You still need to be inside the bin directory to work with psql

I had your issue and got it working again (on windows 7).

I deleted the PATH variables above one at a time to test if they were both really needed. Psql continued to work after I deleted the lib path, but stopped working after I deleted the bin path. When I returned bin, it still didn’t work, and the same with lib. I closed and reopened the command line between tries, and checked the path. The problem lingered even though the path was identical to how it had been when working. I re-pasted it.

I uninstalled and reinstalled postgres. The problem lingered. It finally worked after I deleted the spaces between the «; C. » in the paths and re-saved.

Not sure if it was really the spaces that were the culprit. Maybe the environment variables just needed to be altered and refreshed after the install.

I’m also still not sure if both lib and bin paths are needed since there seems to be some kind of lingering memory for old path configurations. I don’t want to test it again though.

Источник

10 ответов

Лучший ответ

C:UsersLENOVODocumentspostgresql-9.5.21-1-windows-x64-binaries (1)pgsqlbin

C:usrlocalpgsqldata

C:UsersLENOVODocumentspostgresql-9.5.21-1-windows-x64-binaries (1)pgsqlbin>pg_ctl -D "C:usrlocalpgsqldata" start

C:Program FilesPostgreSQL[YOUR PG VERSION]bin

C:Program FilesPostgreSQL10bin
C:Program FilesPostgreSQL10lib

;C:Program FilesPostgreSQL9.5bin;C:Program FilesPostgreSQL9.5lib

;C:Program FilesPostgreSQL9.5bin ;C:Program FilesPostgreSQL9.5lib

;C:Program FilesPostgreSQL[Your Version]bin ;C:Program FilesPostgreSQL[Your Version]lib

pg_ctl -D "C:Program FilesPostgreSQL11.4data" start