a year ago
i'm getting this error quite often:
PostgreSQL connection: Error { kind: Db, cause: Some(DbError { severity: "FATAL", parsed_severity: Some(Fatal), code: SqlState(E57P01), message: "terminating connection due to administrator command", detail: None, hint: None, position: None, where_: None, schema: None, table: None, column: None, datatype: None, constraint: None, file: Some("postgres.c"), line: Some(3318), routine: Some("ProcessInterrupts") }) }
Occationally multiple times per second. I have no idea what causes this, I cannot reproduce it locally when I connect to the same database, so unsure whether this is railway related or neon (the database hosting provider).
Any ideas?
Thanks in advance!
3 Replies
a year ago
This is likely related to neon and connection limits that they have.
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
prisma:error Error in PostgreSQL connection: Error { kind: Db, cause: Some(DbError { severity: "FATAL", parsed_severity: Some(Fatal), code: SqlState(E57P01), message: "terminating connection due to administrator command", detail: None, hint: None, position: None, where_: None, schema: None, table: None, column: None, datatype: None, constraint: None, file: Some("postgres.c"), line: Some(3289), routine: Some("ProcessInterrupts") }) }
getting the same issue for koyeb database service
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
Hello,
We don't have any restrictions on outbound connections in anyway shape or form.
You would need to get in contact with the external database providers for support with their databases.
Best,
Brody
Status changed to Awaiting User Response Railway • about 1 year ago
9 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 10 months ago