No sir, no problem. Thanks for the info
In my case, it was because I had scram-sha-256 and not trust as the auth mechanism.
Because scram-sha-256 requires a physical user.
You can probably work around that by creating a user map in pg_ident.conf but I’m not sure how.
If by “physical user” you mean “Unix system user” then no, scram-sha-256 does not require such a user configured on the system. The peer method requires a system user, and trust is just a terrible idea all around when you’re using a remote database server.
Will we have to include the following in addition to the existing process ?
CREATE EXTENSION vector;
since I see this extension in the discourse_docker postgres template ?
זה משמש את תוסף הליבה של Discourse AI, כך שתצטרך אותו אם אתה משתמש בו.
I don’t remember enabling that plugin. Infact I just checked that it is disabled. But recently when i rebuilt the image, when the latest commit went beyond this commit - GitHub - discourse/discourse at 0eab7daea450e1d7e416c46a23aaaf95687d4855, rake db:migrate started failing. When i used the commit just before the above one to bootstrap, it continued to work.
Now that I have enabled this extension, commits later than this is working without issues.
אבל עכשיו תוסף ה-AI נמצא בליבה, אז אתה צריך את ההרחבה ללא קשר אם אתה משתמש בתוסף ה-AI (או ממציא דרך להסיר אותו במפורש), נכון?
אה, זה נכון, מכיוון שהמיגרציות מופעלות באופן עצמאי מהפעלת התוסף.