The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

postgresql limit

Discussion in 'General Discussion' started by flipper, Apr 3, 2004.

  1. flipper

    flipper Member

    Joined:
    Sep 14, 2002
    Messages:
    20
    Likes Received:
    0
    Trophy Points:
    1
    We have a server that has a problem with listing the number of PostgreSQL databases being used by each user. All of the users control panels show that they are using three databases even when they haven't created any databases. Even new accounts show three PostgreSQL databases used the first time that you log into their control panel. I've updated to the latest stable version, but the server is still having the same problem. Can anyone tell me how to correct this?

    Thanks,
    Larry
     
  2. Ali

    Ali Well-Known Member

    Joined:
    Jul 12, 2003
    Messages:
    52
    Likes Received:
    0
    Trophy Points:
    6
    we are facing the exact same problem. Anyone with a fix?
     
  3. chud67

    chud67 Member

    Joined:
    Feb 9, 2004
    Messages:
    24
    Likes Received:
    0
    Trophy Points:
    1
    * bump *
     
  4. cyberspirit

    cyberspirit BANNED

    Joined:
    Jun 27, 2003
    Messages:
    293
    Likes Received:
    0
    Trophy Points:
    0
  5. Ali

    Ali Well-Known Member

    Joined:
    Jul 12, 2003
    Messages:
    52
    Likes Received:
    0
    Trophy Points:
    6
    Reinstalled postregsql and it fixed the issue.
     
  6. alex042

    alex042 Well-Known Member

    Joined:
    Sep 13, 2003
    Messages:
    76
    Likes Received:
    0
    Trophy Points:
    6
    Or just restart postgresql periodically so it recounts databases.
     
  7. Ali

    Ali Well-Known Member

    Joined:
    Jul 12, 2003
    Messages:
    52
    Likes Received:
    0
    Trophy Points:
    6
    Yeah I figured that. Even after rebooting the server it's shows incorrect usage. Manually restarting Postgre server corrects it.
     
Loading...

Share This Page