Sample location for pg_hba.conf: /etc/postgresql/9.1/main/pg_hba. Safely (though SSL certificate authentication might be a better choice If theĬonnection is protected by SSL encryption then password can be used However, md5 cannot be used with the db_user_namespace feature. The true solution is to repair your broken table design and use a numeric type for your numeric data in area and duration. Cast that 0 to text (Or just quote it) or duration to integer. COALESCE types text and integer cannot be matched. Plain password should always be avoided if possible. SELECT coalesce (area::text, 0) as area, coalesce (duration::text, 0) as duration. If you are at all concerned about password "sniffing" attacks then md5 Methods operate similarly except for the way that the password is sentĪcross the connection, namely MD5-hashed and clear-text respectively. The password-based authentication methods are md5 and password. Operating system user name from the kernel and using it as the allowedĭatabase user name (with optional user name mapping). The peer authentication method works by obtaining the client's These are brief descriptions of both options according to the official PostgreSQL docs on authentication methods. If you're on Linux, that would be sudo service postgresql restart. The command locate pg_hba.conf should help here's some examples: /etc/postgresql/*/main/pg_hba.conf and /var/lib/pgsql/data/pg_hba.conf.Īfter altering this file, don't forget to restart your PostgreSQL server. * The location of this file isn't very consistent. The problem is still your pg_hba.conf file*.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |