Skip to content
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

DB limit open connections #1557

Closed
Legogris opened this issue Aug 18, 2019 · 2 comments
Closed

DB limit open connections #1557

Legogris opened this issue Aug 18, 2019 · 2 comments

Comments

@Legogris
Copy link
Contributor

When using Postgresql as a database, we see that despite very low activity, new connections keep getting opened and are left idle.

I see that open connections are already limited for Sqlite:

db.DB().SetMaxOpenConns(1)

I see a couple of options here:

@Legogris Legogris changed the title DB connection limit DB limit open connections Aug 18, 2019
@se3000
Copy link
Contributor

se3000 commented Jan 31, 2020

@Legogris we believe this has been fixed now. We have improved the database locking logic. Are you still seeing this error?

@se3000
Copy link
Contributor

se3000 commented May 20, 2020

No response. We believe this is fixed with the new Postgres locking strategy. Please reopen if you continue to run into the issue.

@se3000 se3000 closed this as completed May 20, 2020
mateusz-sekara pushed a commit that referenced this issue Jan 10, 2025
Lombard send full payload if attestation is disabled. It can be enabled
by redeploying token pools and synchronizing this between chains.
If mistake took place and we got a message with full payload while
attestation is enabled onchain at Lombard side, message will be
available for manual exec
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

No branches or pull requests

2 participants