Re: FW: Error!

Поиск
Список
Период
Сортировка
От postgresql439848@heinz-it.de
Тема Re: FW: Error!
Дата
Msg-id b8807206-c2b2-f2af-a615-e640631dd9c1@heinz-it.de
обсуждение исходный текст
Ответ на Re: FW: Error!  (Adrian Klaver <adrian.klaver@aklaver.com>)
Ответы RE: FW: Error!  (Arquimedes Aguirre <puntal8@hotmail.com>)
Список pgsql-general
Am 25.04.23 um 17:02 schrieb Adrian Klaver:
On 4/25/23 07:31, postgresql439848@heinz-it.de wrote:
Am 25.04.23 um 01:16 schrieb Arquimedes Aguirre:

No, it has not changed the error that I have been experiencing since the beginning. This is the error:

psql: error: connection to server at "localhost" (::1), port 5432 failed: FATAL: password authentication failed for user "punta" Press any key to continue . .

...

Hi,

is it possible that postgres is listening on ipv4(127.0.0.1) only and you trying connect to ipv6(::1)?

try connect to 127.0.0.1 as "server" instead of "localhost".


Then you would get this error:

psql: error: connection to server at "::1", port 5432 failed: Connection refused
Is the server running on that host and accepting TCP/IP connections?

OK, my mistake.
but is there a possibility to put in the same (may be copy/paste) credentials with different clients and cause this error?

spoiler: there are many and the password 123456 was invented for this case.
conclusion: after a few tests i would bet on a password which causes an ugly hiccup and this could be not users fail.

testing:
- windows installer with default settings, password is quite simple 123456.
- in pgadmin create a new role with "special" password(i take the german specialties üöä or even some symbols). no errors.
- in pgadmin add new server with credentials of new role ... automatic try to connect. connected!
looks like there is nothing wrong at all.

BUT
- start the "SQL Shell" or try psql directly.
- default settings(localhost:5432:postgres:postgres) and the simple password 123456
- connected. may be a warning about encoding/codepage, but connected.

try credentials for new role. result: see TO first/last message.
try change codepage (the docs says 1252 is appropriate for german). same result.
password file in ANSI, same result.

conclusion: see above


the hardest fail:
i tried first of all something like "special" password for superuser during installation and get lost without any idea why.

error: "failed to load SQL modules into the database cluster."
next one follows, warning: "Problem running post-install step. Installation may not complete correctly
Error reading file C:/Program Files/PostgreSQL/15/data/postgresql.conf"
result: initialization failed, data directory doesn't exist.
the final shot is the installation-summary log, no errors, no comments about that even something could be not as expected.

how someone would see this and get to understanding that his/her keyboard has wrong keys to type right passwords?


PS to whom it may concern:
it's not my problem and i don't use it this way.
but other people have no choice.
safe the lost souls, do it better, please!

A.H.

В списке pgsql-general по дате отправления:

Предыдущее
От: "Peter J. Holzer"
Дата:
Сообщение: Re: DBD::Pg (version 3.16.3) returns EMPTY char columns as 'undef'
Следующее
От: Matthias Apitz
Дата:
Сообщение: Re: DBD::Pg (version 3.16.3) returns EMPTY char columns as 'undef'