News for hackers. Stuff that matters.

A comment on Why Uber Engineering Switched from Postgres to MySQL (2016). Parent comment

Re:Why Uber Engineering Switched from Postgres to MySQL (2016) by tinus_hn on Saturday February 27, 2021 @07:13AM (#26284340)
It would be great if there was some management GUI for these tasks so you don’t have to look up the syntax for these things that in many deployments you only do once.
[ Parent | on HN ]
Re:Why Uber Engineering Switched from Postgres to MySQL (2016) by rektide on Saturday February 27, 2021 @01:44PM (#26287037)
both kubernetes operators have some ok user management built in
[ Parent | on HN ]
Re:Why Uber Engineering Switched from Postgres to MySQL (2016) by mvanbaak on Saturday February 27, 2021 @08:23AM (#26284690)
pgadmin ;-P
[ Parent | on HN ]
Re:Why Uber Engineering Switched from Postgres to MySQL (2016) by tinus_hn on Saturday February 27, 2021 @09:50AM (#26285181)
This actually looks pretty reasonable, I am going to look into it. First I need to figure out how to open up the server for connections but still limit it, though.
[ Parent | on HN ]
Re:Why Uber Engineering Switched from Postgres to MySQL (2016) by jhauris on Saturday February 27, 2021 @10:20AM (#26285364)
Look at the pg_hba.conf file (probably something like /etc/postgresql/<version>/main/pg_hba.conf).

https://www.postgresql.org/docs/current/auth-pg-hba-conf.htm...

[ Parent | on HN ]
Re:Why Uber Engineering Switched from Postgres to MySQL (2016) by tinus_hn on Saturday February 27, 2021 @05:39PM (#26288826)
Perhaps it’s better to only listen to localhost and connect through a SSH proxy connection
[ Parent | on HN ]
Re:Why Uber Engineering Switched from Postgres to MySQL (2016) by rleigh on Saturday February 27, 2021 @05:36PM (#26288802)
Or DataGrip if you already have a JetBrains licence.
[ Parent | on HN ]