Results 1 to 3 of 3
  1. #1
    Join Date
    Aug 2016

    Unanswered: Connecting to Postgres database using Sql Developer without root privileges

    I use SqlDeveloper to connect to PostgreSql databases. However, when you connect that way you have to first connect to the root user (postgres / postgres by default). The reason is that the database entry is a non-editable combo box that is populated when you click "select database" while connected as root. Once the list is populated you can then select a database and enter the username and password for that database. There is no way to directly enter a database in the user interface.

    Is there a configuration file or some other way to connect to postgres with SqlDeveloper without having to connect to the root user. Our sys admin recently changed the password and we no longer have access to that account.
    Last edited by Bobt1234; 03-16-17 at 17:40.

  2. #2
    Join Date
    Nov 2003
    Provided Answers: 23
    You don't need a "root" connection (assuming you mean the superuser "postgres").

    Just enter your regular username and password.

    If that is correct you can click on "Choose database" and the drop down will be populated (tested with SQL Developer 4.1). Every user can see the list of all database.
    I will not read nor answer questions where the SQL code is messy and not formatted properly using [code] tags:

    Tips for good questions:

  3. #3
    Join Date
    Aug 2016

    Connecting to PostgreSql from SqlDeveloper without super user privileges

    That didn't work for me. Maybe because the user and the database name are not the same.

    If the user is (let's say) Weather_admin and the database is Weather_db and the password is 1234.

    This used to work:
    Connect to "postgres / postgres", click "select database" and all databases on the server were displayed.
    Now I get.
    Error, invalid password.

    If I set user name to "Weather_admin" and password to "1234" and click select database I get.
    Error, database "Weather_admin" doesn't exist.

    I think I may have a work-around. Create an identical database on localhost, connect to my local machine's superuser (postgres / postgres), click select database and select the dummy "Weather_db" on my local machine (which has nothing in it).

    Then change the host to the server IP, the user name to Weather_admin and the password to 1234. The database is already populated so it should work. It's a bogus solution but we'll see.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts