7ca80dd7-b76f-4860-8cd5-add39d3a162c

your app should be using a database pool, not opening a new connection for every query you make to the database

Oh okay thanks. I will look into that.
In the meantime, how can I uncrash my database?

well its not crashed, just not accepting any more connections, you can redeploy it to close the connections

@Brody Wait, I'm actually not opening a new connection each time… I don't think. Becuase I open it once and then make it a global variable called db.

```go
package main

import (
"database/sql"
//"os"
"fmt"

_ "github.com/lib/pq"

)

var db *sql.DB

func InitDB( /dbname string, password string, host string, port string, user string/ ) {

var err error

//    "dbname="+dbname+" user="+user+" password="+password+" host="+host+" port="+port+" sslmode=disable"

db, err = sql.Open("postgres", "postgresql://postgres:4B...beB1fd@monorail.proxy.rlwy.net:47665/railway")

if err != nil {
    fmt.Println("InitDB err")
    panic(err)
} else {
    fmt.Println("Connected to DB")
}

}```

I then use the global db object throughout code

is there anything else connecting to yoour database?

No, only one app

ChatGPT said to add
go db.SetMaxOpenConns(25) // Maximum number of open connections to the database db.SetMaxIdleConns(25) // Maximum number of idle connections in the pool db.SetConnMaxLifetime(5 * 60)

Do you think this is the solution? Or should have pooling alone fixed the problem?

is that even valid code?

Project code or postgres code?

I put … inside the postgres code, I assume I shouldn't make it public

code for github.com/lib/pq

Oh

Good question let me check

https://pkg.go.dev/database/sql#DB.SetMaxIdleConns

then cant hurt to try

Okay I'll try

Also, is it the constant reading from the database that's the issue or the constant changing of a value? Or it doesn't matter?

it would be too many connections being open to the database, but i honestly dont know why that would happen