| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Mohammed falih <moh(dot)falih98(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: The postgres server don't work |
| Date: | 2022-01-08 23:51:48 |
| Message-ID: | 3af5f6f3-49e0-8192-7e5a-4e05dee3f61d@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 1/8/22 15:29, Mohammed falih wrote:
> yes I think the service doesn't even start
>
> I have only the default protection that comes with the operating system
>
> wow the postgres started working!! but the problem came back that talks
> about console code " WARNING: Console code page (437) differs from
> Windows code page (1252)
>
> 8-bit characters mightnot work correctly. See psql reference
> page "Notes for Windows users"for details."
>
I don't use Windows anymore so I am going from memory here. In the
Windows menu there should be an entry for Postgres and its sub-programs.
One of those should be named something like psql or database shell.
Click on that, it will run a shell script that prompts you for
connection information and if I remember correctly also takes care of
the above issue.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alicja Kucharczyk | 2022-01-09 01:15:03 | Re: create database hangs forever on WSL - autovacuum deadlock? |
| Previous Message | Adrian Klaver | 2022-01-08 23:40:49 | Re: The postgres server don't work |