Skip to content

fix: make a separate server connection for each database in config and route client connections properly - #14

Open
jedwards1211 wants to merge 1 commit into
johto:masterfrom
jcoreio:fix-db-conns
Open

fix: make a separate server connection for each database in config and route client connections properly#14
jedwards1211 wants to merge 1 commit into
johto:masterfrom
jcoreio:fix-db-conns

Conversation

@jedwards1211

@jedwards1211 jedwards1211 commented Feb 26, 2026

Copy link
Copy Markdown
Contributor

fix #12

Maybe you intended something completely different with databases, but this makes it behave how I expected: allas creates a separate pq.Listener and NotifyDispatcher for each of the entries in databases, and passes the map of NotifyDispatchers to FrontendConnection. Then the FrontendConnection picks the NotifyDispatcher to use from the map based upon the database name in the auth packet.

Again I'm new to Go so I don't really know if I'm doing anything dumb in these changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support multiple database connections?

1 participant