StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18007600
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
2013-08-02T11:52:46.470
CreationDate
2013-08-02T02:04:28.077
FavoriteCount
0
LastActivityDate
2015-01-12T20:18:31.787
LastEditDate
2017-05-23T12:17:16.923
LastEditorUserId
-1
OwnerUserId
926143
ParentId
17971101
PostTypeId
2
Score
11
ViewCount
0
LastEditorDisplayName
text
Body
List of errors encountered and solved: <ol> <li>shell-init: error retrieving current directory: getcwd: cannot access parent directories: Permission denied</li> <li>pg_config error</li> <li>Library not loaded: libpq.5.dylib</li> <li>fe_sendauth: no password supplied </li> <li>pg_ctl: no database directory specified and environment variable PGDATA unset</li> <li>pg_ctl: server does not shut down</li> <li>(PG::Error)</li> </ol> A) Pre-installation: When you click on the .dmg file to begin installation, a dialog window opens, and there is a README file alongside the installer. Read that. I changed the shared memory as prescribed: <pre><code>$ sudo vi /etc/sysctl.conf On a MacBook Pro with 2GB of RAM, the author's sysctl.conf contains: kern.sysv.shmmax=1610612736 kern.sysv.shmall=393216 kern.sysv.shmmin=1 kern.sysv.shmmni=32 kern.sysv.shmseg=8 kern.maxprocperuid=512 kern.maxproc=2048 </code></pre> I scrolled down the file to the k's and changed each of the listed lines to the specified values. Then you need to reboot your computer. B) Installing and using PostgreSQL: Then click on the .dmg file again, then click on the installer and install postgres. I accepted all the defaults. As far as I can tell, the postgres installer only gives permissions for the directory /Library/PostgreSQL/9.2 to a user named 'postgres'. During the postgres installation, the installer asked for a password for the database superuser, and if you wondered what the database superuser's name was, it's 'postgres'. When you issue the sudo command, you are temporarily changing to the user 'root'. However, the root user does not have access to the dir /Library/PostgreSQL/9.2. So you have to use the su command (switch user) to change to the postgres user. But in order to issue the su command, you need to be the root user. Got that? As a result, whenever you issue postgres commands you need to do this first: <pre><code>$ cd /Library/PostgreSQL/9.2 $ sudo su postgres Password: <normal sudo password> </code></pre> Errors like this: <pre><code>~$ sudo su postgres shell-init: error retrieving current directory: getcwd: cannot access parent directories: Permission denied </code></pre> are caused by the fact that you are trying to switch to the user postgres in a directory where the postgres user does not have permissions, which is, as far as I can tell, every directory except /Library/PostgreSQL/9.2 After you correctly switch to the postgres user: <pre><code>$ cd /Library/PostgreSQL/9.2 $ sudo su postgres Password: <normal sudo password> </code></pre> you get a funny looking prompt. In my case, it looks like this: <pre><code>bash-3.2$ </code></pre> If you issue the ls command: <pre><code>bash-3.2$ ls bin installer scripts data lib share doc pgAdmin3.app stackbuilder.app include pg_env.sh uninstall-postgresql.app </code></pre> you can surmise that you are in the /Library/PostgreSQL/9.2 directory. The enterpriseDB installer automatically starts the postgres server for you when it is done with the installation. If you need to start the server, e.g. you turned your computer off, see "you can stop or start the server from the command line" in step 5 below. C) Connecting to the server using pgAdmin3: I spent hours trying to figure out how to start the server and just generally use postgres with no luck. Then I happened to see something called pgAdmin3 in the dir /Library/PostgreSQL/9.2. I clicked on that, and a window with several panes opened up. In the left pane of the pgAdmin3 window, it says: <pre><code>Server Groups --Servers(1) ----PostgresSQL 9.2 (localhost:5432) </code></pre> I clicked on 'PostgreSQL 9.2 (localhost:5432)' to highlight it, and then I right clicked to bring up a menu, and I chose Connect. When prompted, I entered the database superuser password. D) Setting up rails to use PostgreSQL: Then I followed the directions in this tutorial for getting rails setup: <a href="https://pragtob.wordpress.com/2012/09/12/setting-up-postgresql-for-ruby-on-rails-on-linux/#comment-1142" rel="nofollow noreferrer">https://pragtob.wordpress.com/2012/09/12/setting-up-postgresql-for-ruby-on-rails-on-linux/#comment-1142</a> as follows: 1) The first step is creating a new user. If you use the same name as your mac user name, then you don't have to add a username (or a password) to the database.yml file in your rails app: <pre><code>$ cd /Library/PostgreSQL/9.2 $ sudo su postgres Password: <normal sudo password> bash-3.2$ createuser --interactive 7stud Shall the new role be a superuser? (y/n) n Shall the new role be allowed to create databases? (y/n) y Shall the new role be allowed to create more new roles? (y/n) n Password:<database superuser password> bash-3.2$ </code></pre> That creates a new user with no password. Next, in pgAdmin3 if you click on: <pre><code>---Login Roles(1) </code></pre> to highlight it, and then click on the icon "Refresh the selected object" at the top of the window, you will see the new user displayed. The postgres docs for createuser are here: <a href="http://www.postgresql.org/docs/9.2/interactive/app-createuser.html" rel="nofollow noreferrer">http://www.postgresql.org/docs/9.2/interactive/app-createuser.html</a> There is also a dropuser command: <pre><code>bash-3.2$ dropuser 7stud </code></pre> 2) Then add the 'pg' gem to your Gemfile, and comment out the sqlite gems. 3) Then try to install the pg gem with Bundler: <pre><code>rails_projects/sample_app/$ bundle install --without production </code></pre> When I tried that, I got a 'pg_config' error. To fix that error, I followed the advice here: <a href="http://excid3.com/blog/installing-postgresql-and-pg-gem-on-mac-osx/#.UftQUOB6gy6" rel="nofollow noreferrer">http://excid3.com/blog/installing-postgresql-and-pg-gem-on-mac-osx/#.UftQUOB6gy6</a> and added /Library/PostgreSQL/9.2 to my PATH (I do all PATH manipulations in .bashrc.). Don't forget to 'source' .bashrc or quit Terminal and restart Terminal for the new PATH to take effect. Then I was able to install the pg gem without error: <pre><code>rails_projects/sample_app/$ bundle install --without production rails_projects/sample_app/$ bundle update rails_projects/sample_app/$ bundle install </code></pre> (I don't really understand why you have to do all three of those commands, but that is what railstutorial does.) 4) Next change your config/database.yml file. For each of the sections: test, development, and production change the 'adapter' and 'database' lines, and add an 'encoding' line, e.g.: <pre><code>development: adapter: postgresql database: ArbitaryDatabaseName (e.g. sampleapp_dev) encoding: utf8 pool: 5 timeout: 5000 </code></pre> Make sure all three database lines specify a different name. 5) Then try to create the databases: <pre><code>rails_projects/sample_app/$ bundle exec rake db:create:all </code></pre> When I tried that, I got the error: <pre><code>dlopen(/Users/7stud/.rvm/gems/ruby-2.0.0-p247@railstutorial_rails_4_0/gems/pg-0.15.1/lib/pg_ext.bundle, 9): Library not loaded: libpq.5.dylib Library not loaded: libpq.5.dylib Referenced from: /Users/7stud/.rvm/gems/ruby-2.0.0-p247@railstutorial_rails_4_0/gems/pg-0.15.1/lib/pg_ext.bundle </code></pre> The library libpq.5.dylib is located in <pre><code>/Library/PostgreSQL/9.2/lib </code></pre> Using the suggestions here: <a href="https://github.com/PostgresApp/PostgresApp/issues/109" rel="nofollow noreferrer">https://github.com/PostgresApp/PostgresApp/issues/109</a> I solved that error by adding the following to my .bashrc file(or you can put it in .bash_profile): <pre><code>export DYLD_FALLBACK_LIBRARY_PATH="/Library/PostgreSQL/9.2/lib:$DYLD_LIBRARY_PATH" </code></pre> (Remember to 'source' .bashrc or exit Terminal and start a new Terminal window.) Then I tried to create the databases again: <pre><code>rails_projects/sample_app/$ bundle exec rake db:create:all fe_sendauth: no password supplied … </code></pre> To solve that blasted error, you need to change the pg_hba.conf file, which is in the directory <pre><code>/Library/PostgreSQL/9.2/data </code></pre> You can't go into that directory using Finder--you have to use the postgres user to go into that directory: <pre><code>$ cd /Library/PostgreSQL/9.2 $ sudo su postgres Password: <normal sudo password> bash-3.2$ cd data bash-3.2$ ls PG_VERSION pg_hba.conf pg_notify pg_subtrans postgresql.conf base pg_ident.conf pg_serial pg_tblspc postmaster.opts global pg_log pg_snapshots pg_twophase postmaster.pid pg_clog pg_multixact pg_stat_tmp pg_xlog bash-3.2$ mvim pg_hba.conf (or instead of mvim open with another text editor, e.g. vim) </code></pre> In the .conf file you need to change 'md5' to 'trust': <pre><code># TYPE DATABASE USER ADDRESS METHOD # "local" is for Unix domain socket connections only local all all trust #md5 # IPv4 local connections: host all all 127.0.0.1/32 trust #md5 # IPv6 local connections: host all all ::1/128 trust #md5 # Allow replication connections from localhost, by a user with the # replication privilege. #local replication postgres md5 #host replication postgres 127.0.0.1/32 md5 #host replication postgres ::1/128 md5 </code></pre> The access METHOD 'md5' means the database is expecting an encrypted password for the specified database users. But when you created the new user, you created it without a password. The access METHOD 'trust' means the database does not expect a password. Then I tried to create the databases again: <pre><code>rails_projects/sample_app/$ bundle exec rake db:create:all fe_sendauth: no password supplied … </code></pre> In an attempt to get the server to read the changes I made in the .conf file, I disconnected from the server in pgAdmin3: <pre><code>Server Groups --Servers(1) ----PostgresSQL 9.2 (localhost:5432) Click on PostgresSQL 9.2 (localhost:5432) to highlight it, right click, then select Disconnect, then right click and select Connect. </code></pre> But apparently that wasn't working. Disconnecting and reconnecting to the server does not cause the server to reload the .conf file. To get the server to reload the .conf file, in pgAdmin3 you can right click on <code>PostgresSQL 9.2 (localhost:5432)</code> and select: <pre><code>Reload configuration </code></pre> Or you can stop and then start the server from the command line: (Note the following commands assume you have already switched to the postgres user, see "Installing and using PostgreSQL" above.) <pre><code>bash-3.2$ cd /Library/PostgreSQL/9.2/ bash-3.2$ pg_ctl stop (First disconnect from the server in pgAdmin3) </code></pre> However, that produced the error: <pre><code>pg_ctl: no database directory specified and environment variable PGDATA unset Try "pg_ctl --help" for more information. </code></pre> I solved that error like this: <pre><code>bash-3.2$ export PGDATA=/Library/PostgreSQL/9.2/data bash-3.2$ echo $PGDATA /Library/PostgreSQL/9.2/data bash-3.2$ pg_ctl stop waiting for server to shut down.... done server stopped bash-3.2$ pg_ctl start server starting </code></pre> If you don't disconnect from the server first in pgAdmin3, you get the output: <pre><code>bash-3.2$ pg_ctl stop waiting for server to shut down............................................................... failed pg_ctl: server does not shut down HINT: The "-m fast" option immediately disconnects sessions rather than waiting for session-initiated disconnection. bash-3.2$ </code></pre> Later, I was unable to shut down the server when I had the rails console open. I added a User to the database using <code>User.create(....)</code>, and I forgot to start postgres beforehand, so I wondered what was going to happen to that record. For some reason, the postgress server was already running on my system(it seems that postgress starts every time I boot my computer--solved below). Next, I tried to stop the server, and I was unable to. After closing the rails console, the server stopped. Finally, no errors: <pre><code>~/rails_projects/sample_app4_0$ bundle exec rake db:create:all ~/rails_projects/sample_app4_0$ bundle exec rake db:migrate ~/rails_projects/sample_app4_0 </code></pre> I guess that means the db's were created. If you look in pgAdmin3, you should be able to see three new databases (although they have red x's on them). If you can't see them, right click on the Databases directory(in pgAdmin3) and select Refresh. Edit: I ran into some problems later. To fully test if things are working, see here: <a href="https://stackoverflow.com/questions/18094845/how-do-i-get-my-rails-app-to-use-my-postgresql-db">How do I get my rails app to use my postgresql db?</a> 6) Guard/Spork When I started up my Guard/Spork combination: <pre><code>~/rails_projects/sample_app4_0$ bundle exec guard </code></pre> I got this error: <pre><code>... ... Preloading Rails environment Loading Spork.prefork block... FATAL: the database system is shutting down (PG::Error) </code></pre> I fixed that by starting the postgres server, and using pgAdmin3 to connect to the server. Eventually, I figured out how to keep the postgres server from starting every time I boot my computer. I had to make two changes: 1) <code>$ sudo vim /Library/LaunchDaemons/com.edb.launchd.postgresql-9.2.plist</code> Substitute your version of postgres in place of 9.2. 2) Locate the line RunAtLoad 3) Change the next line from <code><true/></code> to <code><false/></code> <a href="https://superuser.com/questions/244589/prevent-postgresql-from-running-at-startup">https://superuser.com/questions/244589/prevent-postgresql-from-running-at-startup</a> Those steps alone did not work for me. Then I found this advice: 4) <code>$ sudo launchctl unload -w /Library/LaunchDaemons/com.edb.launchd.postgresql-9.2.plist</code> Substitute your version of postgres in place of 9.2. <a href="http://www.postgresql.org/message-id/flat/4B41FD48.7030009@enterprisedb.com#4B41FD48.7030009@enterprisedb.com" rel="nofollow noreferrer">http://www.postgresql.org/message-id/flat/4B41FD48.7030009@enterprisedb.com#4B41FD48.7030009@enterprisedb.com</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow do I start enterpiseDB PostgreSQL on Mac OSX 10.6.8?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. US7stud
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow do I start enterpiseDB PostgreSQL on Mac OSX 10.6.8?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.