StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>The problem is still your <code>pg_hba.conf</code> file (/etc/postgresql/9.1/main/pg_hba.conf*). This line:</p> <pre><code>local all postgres peer </code></pre> <p>Should be</p> <pre><code>local all postgres md5 </code></pre> <p>* If you can't find this file, running <code>locate pg_hba.conf</code> should show you where the file is.</p> <p>After altering this file, don't forget to restart your PostgreSQL server. If you're on Linux, that would be <code>sudo service postgresql restart</code>.</p> <p>These are brief descriptions of both options according to the <a href="http://www.postgresql.org/docs/9.3/static/auth-methods.html" rel="noreferrer">official PostgreSQL docs on authentication methods</a>.</p> <h3>Peer authentication</h3> <blockquote> <p>The peer authentication method works by obtaining the client's operating system user name from the kernel and using it as the allowed database user name (with optional user name mapping). This method is only supported on local connections.</p> </blockquote> <h3>Password authentication</h3> <blockquote> <p>The password-based authentication methods are md5 and password. These methods operate similarly except for the way that the password is sent across the connection, namely MD5-hashed and clear-text respectively.</p> <p>If you are at all concerned about password "sniffing" attacks then md5 is preferred. Plain password should always be avoided if possible. However, md5 cannot be used with the db_user_namespace feature. If the connection is protected by SSL encryption then password can be used safely (though SSL certificate authentication might be a better choice if one is depending on using SSL).</p> </blockquote> <p>Sample location for <code>pg_hba.conf</code></p> <blockquote> <p>/etc/postgresql/9.1/main/pg_hba.conf</p> </blockquote>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload