Console code page 437 differs from windows code page 1252

Whenever I access psql, I get the following message:

psql (9.6.2)
WARNING: Console code page (437) differs from Windows code page (1252)
     8-bit characters might not work correctly. See psql reference
     page "Notes for Windows users" for details.
Type "help" for help.

postgres=#

I tried command

cmd.exe /c chcp 1252

before running runpsql.bat file in command line. And there, it runs fine without the error. But accessing psql again after closing command prompt, throws the same warning. How do I solve this warning within SQL Shell?

I am using windows 10 OS.

Edit:

This is what I did:

Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:UsersSarthak Joshi>E:

E:>cd PostgreSQL

E:PostgreSQL>cd scripts

E:PostgreSQLscripts>chcp 1252
Active code page: 1252

E:PostgreSQLscripts>runpsql.bat
Server [localhost]:
Database [postgres]:
Port [5432]:
Username [postgres]:
Password for user postgres:
psql (9.6.2)
Type "help" for help.

postgres=#

But after exiting from cmd, and firing up shell like this:

Server [localhost]:
Database [postgres]:
Port [5432]:
Username [postgres]:
Password for user postgres:
psql (9.6.2)
WARNING: Console code page (437) differs from Windows code page (1252)
         8-bit characters might not work correctly. See psql reference
         page "Notes for Windows users" for details.
Type "help" for help.

postgres=#

It still throws the same warning…

SUMMARY OF PROBLEM: Postgres notes no errors upon installation, but upon
startup of psql there’s a warning; documentation fix doesn’t eliminate
the warning message.

1. psql says this when I log in:

Server [localhost]:

Database [postgres]:

Port [5432]:

Username [postgres]:

Password for user postgres:

psql (9.4rc1)

WARNING: Console code page (437) differs from Windows code page (1252)

8-bit characters might not work correctly. See psql reference

page «Notes for Windows users» for details.

Type «help» for help.

postgres=#

2. psql ref. pg. says this:

*Notes for Windows Users*

psql is built as a «console application». Since the Windows console
windows use a different encoding than the rest of the system, you must
take special care when using 8-bit characters within psql. If psql
detects a problematic console code page, it will warn you at startup. To
change the console code page, two things are necessary:

* Set the code page by entering cmd.exe /c chcp 1252. (1252 is a code
page that is appropriate for German; replace it with your value.) If
you are using Cygwin, you can put this command in /etc/profile.

Set the console font to Lucida Console, because the raster font does not
work with the ANSI code page.

3. When I enter «cmd.exe /c chcp 1252» into the command prompt, it says
this:

Microsoft Windows [Version 6.1.7600]

Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:Userszzzzzz>cmd.exe /c chcp 1252

Active code page: 1252

C:Userszzzzzz>

4. Am I supposed to type this at the command prompt: «cmd.exe /c chcp
437″? Because that’s what I did, and now the command prompt says this…

C:Userszzzzzz>cmd.exe /c chcp 437

Active code page: 437

C:Userszzzzzz>

…but I quit and reopened psql, the error message isn’t gone or changed.

5. The instructions to set console font mean nothing to me: «Set the
console font to Lucida Console, because the raster font does not work
with the ANSI code page». Googled it and found nothing that made sense
to me. Set whose console font? PG or Windows? Where and how to set it?
What is a console, anyway? Googled again and again, finally discovered
that the console being referred to is apparently psql itself. By
clicking on the little rectangular icon at the top left of the title bar
of the command prompt (psql), Properties, Font…there it is. «Raster
Fonts» had been selected. I changed this to Lucida Console. Quit psql
and restarted it.

6. psql startup warning has now changed to a different font, no other
change.

7. I changed the console page back to 1252 in the command prompt:

Microsoft Windows [Version 6.1.7600]

Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:Userszzzzz>cd/

C:>cmd.exe /c chcp 1252

Active code page: 1252

C:>

8. Quit and restarted psql (twice). The warning message has not changed.
Is it possible that pg is wrongly detecting code page 437, and does it
matter? I have a lot of work to do and want a sparkling clean foundation
to start from so I don’t have problems later.

—
stumpednomore(at)gmail(dot)com

—
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com

After you login from the command line through psql, you see the message,

      «psql (9.5.1)
        WARNING: Console code page (437) differs from Windows code page (1252)
                              8-bit characters might not work correctly. See psql reference
                              page «Notes for Windows users» for details.
          Type «help» for help.»

This is because Windows console uses a different encoding than the psql console application. To solve this you need to set the code page for your psql before login.

To reset the code page:

           database => q        //log out of the database

           C:Usersdsmith> chcp 1252    //change code page to 1252
           Active code page: 1252

           C:Usersdsmith> psql -d dbname -h host -p port -U username
           Password for user username:
           psql (9.5.1)
           Type «help» for help.

                        
If you have ever asked yourself these questions, this is the book for you. What is the meaning of life? Why do people suffer? What is in control of my life? Why is life the way it is? How can I stop suffering and be happy? How can I have a successful life? How can I have a life I like to have? How can I be the person I like to be? How can I be wiser and smarter? How can I have good and harmonious relations with others? Why do people meditate to achieve enlightenment? What is the true meaning of spiritual practice? Why all beings are one?Read the book free here.

After you install PostgreSQL 14 on Windows, there are a few steps to create a sandbox database. This post shows you those steps, including a couple Windows OS tasks you’ll need to complete. You should note that these instructions are for the PostgreSQL psql Command Line Interface (CLI).

Open a Command Prompt with Administrator privileges. It should give you a command prompt like the following:

Microsoft Windows [Version 10.0.19042.1466]
(c) Microsoft Corporation. All rights reserved.
 
C:Usersusername>

Type psql to launch the PostgreSQL CLI and then the return or enter key:

Most likely, you’ll get the following error message. It means that your System Path environment variable doesn’t include the directory where the psql executable is found, and that’s why the command is not recognized.

'psql' is not recognized as an internal or external command, operable program or batch file.

You can set it temporarily in your current Windows CLI with the following command:

set PATH=%PATH%;C:Program FilesPostgreSQL14bin;

For those familiar with Windows CLI navigation in prior releases, the convention is to append a semicolon at the end of the item added to the %PATH% environment variable. If you were to put the semicolon between the %PATH% and new directory path there would be two semicolons together. While it won’t do any harm, it’s best to follow the new convention or style.

CRITICAL NOTE: The rest of the post assumes you have set the correct %PATH% environment variable or added it to your System’s Path environment variable and restarted the Windows CLI after adding it through the GUI tool. The reason you need to restart the Windows CLI is that the %PATH% environment variable is inherited at startup and doesn’t change in an open Windows CLI shell.

Another common mistake some users make, at least those who have used an older version of the psql utility on a Linux distribution (or “distro”), is to type psql without any arguments to become the superuser. This error doesn’t occur in Linux because you most likely connected as the postgres user before trying to connect to the PostgreSQL database. A quick demonstration should illustrate the error and support explaining why it occurs on the Windows OS.

Attempting to connect to the PostgreSQL database as a non-postgres user:

You should get the following error:

psql: error: connection to server at "localhost" (::1), port 5432 failed: fe_sendauth: no password supplied

This error occurs because you’re not the postgres user, and all other users must designate that they’re connecting to the superuser account. The correct syntax is:

C:Usersusername>psql -U postgres

Then, you’ll be prompted for the password that you set when you installed PostreSQL database. Enter that password from the installation at the prompt.

Password for user postgres:
psql (14.1)
WARNING: Console code page (437) differs from Windows code page (1252)
         8-bit characters might not work correctly. See psql reference
         page "Notes for Windows users" for details.
Type "help" for help.
 
postgres=#

The warning message is telling you that the character set collation differs between your Windows OS and the PostgreSQL database. We’ll discuss this more later but for the sake of almost all your work, it won’t matter. If the warning message bothers you, you can run the chcp command before launching PostgreSQL when you open your Windows CLI:

The chcp command changes your terminal character set to align with the Latin 1 character set, which enables you to use things like non-English accent characters (the umlaut over an o, or ö). After running the You will see this when you connect after running that command:

psql (14.2)
Type "help" for help.
 
postgres#

ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftCommand Processor

Now that you’re connected as the superuser, let’s examine the steps to configure your playground or videodb database. There are five steps to configure your database and one step to connect and use the videodb database as the student user

1. Create Physical Directory

postgres=# show data_directory;

           data_directory
-------------------------------------
 C:/Program Files/PostgreSQL/14/data
(1 row)

1. Create Tablespace

CREATE TABLESPACE video_db
  OWNER postgres
  LOCATION 'C:Usersusernamevideo_db';

SELECT * FROM pg_tablespace;

  oid  |  spcname   | spcowner | spcacl | spcoptions
-------+------------+----------+--------+------------
  1663 | pg_default |       10 |        |
  1664 | pg_global  |       10 |        |
 16395 | video_db   |       10 |        |
(3 rows)

1. Create a Database

postgres=# SELECT datname, datcollate FROM pg_database WHERE datname = 'postgres';

  datname  |         datcollate
-----------+----------------------------
 postgres  | English_United States.1252
(1 row)

CREATE DATABASE videodb
  WITH OWNER = postgres
       ENCODING = 'UTF8'
       TABLESPACE = video_db
       LC_COLLATE = 'English_United States.1252'
       LC_CTYPE = 'English_United States.1252'
       CONNECTION LIMIT = -1;

                                                 List of databases
   Name    |  Owner   | Encoding |          Collate           |           Ctype            |   Access privileges
-----------+----------+----------+----------------------------+----------------------------+-----------------------
 postgres  | postgres | UTF8     | English_United States.1252 | English_United States.1252 |
 template0 | postgres | UTF8     | English_United States.1252 | English_United States.1252 | =c/postgres          +
           |          |          |                            |                            | postgres=CTc/postgres
 template1 | postgres | UTF8     | English_United States.1252 | English_United States.1252 | =c/postgres          +
           |          |          |                            |                            | postgres=CTc/postgres
 videodb   | postgres | UTF8     | English_United States.1252 | English_United States.1252 |
(4 rows)

COMMENT ON DATABASE videodb IS 'Video Store Database';

1. Create a Role, Grant, and User

1. Create a Schema

GRANT CREATE ON DATABASE videodb TO student;

SELECT   * 
FROM     pg_catalog.pg_namespace
ORDER BY nspname;

  oid  |      nspname       | nspowner |               nspacl
-------+--------------------+----------+-------------------------------------
 16399 | app                |    16398 |
 13388 | information_schema |       10 | {postgres=UC/postgres,=U/postgres}
    11 | pg_catalog         |       10 | {postgres=UC/postgres,=U/postgres}
    99 | pg_toast           |       10 |
  2200 | public             |       10 | {postgres=UC/postgres,=UC/postgres}
(5 rows)

-- Set client messages to warning or error, which means any
-- notice associated with the if exists clause is suppressed.
SET client_min_messages TO warning;
 
-- Conditionally drop an existing revision_history table in
-- the app schema.
DROP TABLE IF EXISTS revision_history;
 
-- Create a revision_history table.
CREATE TABLE app.revision_history
( revision_history_id serial
, session_id          VARCHAR
, table_name          VARCHAR
, revision_id         INTEGER );

Did not find any relation named "revision_history".

   search_path   
-----------------
 "$user", public
(1 row)

SET search_path TO app, "$user", public;

                                                  Table "app.revision_history"
       Column        |       Type        | Collation | Nullable |                            Default                            
---------------------+-------------------+-----------+----------+---------------------------------------------------------------
 revision_history_id | integer           |           | not null | nextval('revision_history_revision_history_id_seq'::regclass)
 session_id          | character varying |           |          | 
 table_name          | character varying |           |          | 
 revision_id         | integer           |           |          |

1. Connect as student to videodb:

psql -d videodb -U student -W

Password:
psql (14.1)
WARNING: Console code page (437) differs from Windows code page (1252)
         8-bit characters might not work correctly. See psql reference
         page "Notes for Windows users" for details.
Type "help" for help.
 
videodb=>

SELECT current_database();

 current_database 
------------------
 videodb
(1 row)

This has shown you how to create a videodb tablespace, a videodb database, a dba role, a student user, an app schema, and connect to your new videodb database as the student user. As always, I hope it lets you get a lot down with little effort and avoiding pages and pages of documentation.

I have installed two versions of Postgresql, 8.4 and 9.1. When I try to run psql it only picks up the previous psql version. For example, when I run the following line to connect to the database, ax_data:

C:Program Files (x86)PostgreSQL9.1bin>psql ax_data
Password:
psql (9.1.2, server 8.4.8)
WARNING: psql version 9.1, server version 8.4.
         Some psql features might not work.
WARNING: Console code page (437) differs from Windows code page (1252)
         8-bit characters might not work correctly. See psql reference
         page "Notes for Windows users" for details.
Type "help" for help.

ax_data=

It is not finding the more recent psql installation. When using pgAdmin, if I click on psql a small command window pops up, but when I type commands in nothing is happening. I’m not very experienced with Postgresql so I could have made some basic mistake somewhere along the way. Any thoughts on what I could be doing wrong?

EDIT:

I am able to login using:

C:>C:"Program Files (x86)"PostgreSQL9.1binpsql.exe -p 5434 -U postgres
psql (9.1.2)
WARNING: Console code page (437) differs from Windows code page (1252)
         8-bit characters might not work correctly. See psql reference
         page "Notes for Windows users" for details.
Type "help" for help.

postgres=# LS
postgres-#

but none of the commands seem to work. For example, whenever I type anything in after the prompt, there is no response.