Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8377969
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 9, 20262026-06-09T15:48:36+00:00 2026-06-09T15:48:36+00:00

I got this error from an Play 2.0.3 java application. How could I restart

  • 0

I got this error from an Play 2.0.3 java application. How could I restart Heroku Postgres Dev DB? I could not find any instructions to restart the DB on Heroku help center.

app[web.1]: Caused by: org.postgresql.util.PSQLException: FATAL: remaining connection slots are reserved for non-replication superuser connections
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-09T15:48:38+00:00Added an answer on June 9, 2026 at 3:48 pm

    The error mesage you have there isn’t a reason to restart the database; it isn’t a database problem. Your application is holding too many connections, probably because you forgot to set up its connection pool. That isn’t a DB server problem and you can fix it without restarting the DB server.

    If you stop your Play application or reconfigure its connection pool the problem will go away.

    Another option is to put your Heroku instance in maintenance mode then take it out again.

    Since heroku doesn’t allow you to connect as a superuser (for good reasons) you can’t use that reserved superuser slot to connect and manage connections like you would with normal PostgreSQL.

    See also:

    Heroku "psql: FATAL: remaining connection slots are reserved for non-replication superuser connections"

    http://wiki.postgresql.org/wiki/Number_Of_Database_Connections

    If you’re a non-heroku user who found this:

    With normal PostgreSQL you can disconnect your client from the server end end using a PostgreSQL connection to your server. See how it says there’s a slot reserved for “superuser connections” ? Connect to Pg as a superuser (postgres user by default) using PgAdmin-III or psql.

    Once you’re connected you can see other clients with:

    SELECT * FROM pg_stat_activity;
    

    If you want to terminate every connection except your own you can run:

    SELECT procpid, pg_terminate_backend(procpid) 
    FROM pg_stat_activity WHERE procpid <> pg_backend_pid();
    

    Add AND datname = current_database and/or AND usename = <target-user-name> as appropriate.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I got this error from XCode: objc[8422]: FREED(id): message release sent to freed object=0x3b120c0
i got this error in the logcat 06-21 11:58:27.275: E/AndroidRuntime(404): java.lang.RuntimeException: Unable to start
I am compiling my first Linux Kernel Module, when i got this error: from
I got streaming error on this site http://68.233.16.160/news/7 says something like 200 stream not
In the Python implementation of FANN, I got this error from from pyfann import
I got an error from my web application which is got from my live
Got this error message while trying to load view: The model item passed into
Got this error on a big $_GET query in size ~9 000 symbols (they
Got this error message while trying to configure an entitydatasource in the designer: My
I got this error when I was installing the SugarCRM on the server: Fatal

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.