![]() It usually doesn’t, but it might be worth a try depending.Īssuming that it hasn’t helped, have a look inside of th e PostgreSQL log to look for errors. In the unlikely case you find something about package errors, then you might be missing one of the SQL modules. More than likely, you’ll actually come across something that warns you that “Permissions should be u=rwx (0700)” and This isn’t usually the cause of these problems, but it certainly can’t hurt to at least have a look. That “data directory “/var/lib/postgresql/9.6/main” has group or world access”, though you might see a different version number depending on which SQL server you’re running. Sudo chown -R postgres:postgres /var/lib/postgresql/9.6/ & sudo chmod -R u=rwX,go= /var/lib/postgresql/9.6/ All you have to do is run the following command at the terminal to fix permissions: This is because Debian and similar distributions expect that the postgres user and group control these directories with 0700 permissions and all files through 0600 permissions for security’s sake. Keep in mind that should be an upper-case X and not the more common lower-case x you’re probably more familiar with due to the specific way that you’re going to want to set these file permission options. While you do need root access to do this, the inclusion of those two sudo marks should be more than enough to give yourself the proper permissions when running as a regular user. This is important since Ubuntu and the various Linux implementations spun off from Ubuntu hash out the main root account so you need to do things this way. Once this command finishes, you can restart the service again by sudo service postgresql restart from the terminal and you shouldn’t have any errors this time. ![]() If you were to take a look at the log, then those warnings regarding permissions problems shouldn’t be there any longer either. This is an error that happens as the result of fairly specific conditions, so you shouldn’t experience it again after you’ve corrected it the first time provided that you don’t try to manually do anything involving permissions manipulation of the PostgreSQL directories. ![]() TypeScript Sequelize : How to join two tables with common.Docker: Docker-compose ruby + postgres - PG::ConnectionBadcould not connect to server.C# with Npgsql - Can't write CLR type System.String with handler type Int32Handler.How to create a synonym for a table in PostgreSQL.Load database dump into postgres database.There’s no situation where this should really be necessary anyway, outside of correcting this problem in the first place. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |