-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
postgres socket connection uses the wrong value for database #2275
Comments
hm, I'm not sure how this is happening. The connection string is a standard Postgres DSN string made out of variables in the config: Line 306 in ad162c2
Line 24 in ad162c2
If you don't have |
Why completed?
I don't see how this was fixed?
…On Tue, 11 Feb 2025, 7:54 pm Kailash Nadh, ***@***.***> wrote:
Closed #2275 <#2275> as completed.
—
Reply to this email directly, view it on GitHub
<#2275 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAL7FE2CTTPO3GKGNA3WLKL2PJBMTAVCNFSM6AAAAABWETBDBKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJWGI3DSNRZHE3DQMQ>
.
You are receiving this because you authored the thread.
Message ID: ***@***.***>
|
Ah, I assumed this was a misconfiguration and was resolved after seeing no response. Please see my previous comment. |
Right, I can confirm you that I have a
just look at these two lines, where just 0.0015 seconds after the databse name apparently changes... Please tell me if and how I could help in debugging. |
@knadh do you have idea where this issue might be coming from? (commenting since this issue is closed, I wouldn't want it to be lost) |
I've been unable to reproduce this, unfortunately. Will leave this open for anyone with time to debug. |
Version:
Description of the bug and steps to reproduce:
Trying to install listmonk using unix socket auth
This shows this on
--install
:It should be noted that:
I then created a database named "myuser", and
--install
proceeded:The log keeps talking about the "listmonk" database, but I verifying that the installation was done on the "myuser" database.
The text was updated successfully, but these errors were encountered: