Postgres_fdw- User Mapping with md5-hashed password
От | Dirschel, Steve |
---|---|
Тема | Postgres_fdw- User Mapping with md5-hashed password |
Дата | |
Msg-id | CH0PR03MB60345DAB1097FFE1D49737B5FAB52@CH0PR03MB6034.namprd03.prod.outlook.com обсуждение исходный текст |
Ответ на | Re: Kubernetes, cgroups v2 and OOM killer - how to avoid? (Joe Conway <mail@joeconway.com>) |
Ответы |
Re: Postgres_fdw- User Mapping with md5-hashed password
|
Список | pgsql-general |
I know I can create user steve_test with password testpassword122 as md5 by doing: select 'md5'||md5('testpassword122steve_test'); Returns --> md5eb7e220574bf85096ee99370ad67cbd3 CREATE USER steve_test WITH PASSWORD 'md5eb7e220574bf85096ee99370ad67cbd3'; And then I can login as steve_test with password testpassword122. I'm trying to use similar logic when creating a user mapping: CREATE USER MAPPING FOR postgres SERVER steve_snap0 OPTIONS (user 'steve_test', password 'md5eb7e220574bf85096ee99370ad67cbd3'); When I try and import a foreign schema I get an error: ERROR: could not connect to server "steve_snap0" If I create the user mapping with the password: CREATE USER MAPPING FOR postgres SERVER steve_snap0 OPTIONS (user 'steve_test', password 'testpassword122'); It works fine. Is it not possible to use the same logic for the user mapping password that can be used when creating a user? Thanks in advance. This e-mail is for the sole use of the intended recipient and contains information that may be privileged and/or confidential.If you are not an intended recipient, please notify the sender by return e-mail and delete this e-mail and anyattachments. Certain required legal entity disclosures can be accessed on our website: https://www.thomsonreuters.com/en/resources/disclosures.html
В списке pgsql-general по дате отправления: