# Rails and PostgreSQL **URL:** \ **Category:** Ruby\ **Created:** [December 7, 2005, 11:45pm UTC](https://www.ruby-forum.com/t/rails-and-postgresql/49718 "2005-12-07T23:45:16Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![colinfreas](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/43a26b/32.png) [@colinfreas](https://www.ruby-forum.com/u/colinfreas)\ **Post date:** [December 7, 2005, 11:45pm UTC](https://www.ruby-forum.com/t/rails-and-postgresql/49718/1 "2005-12-07T23:45:16Z")
I’m trying to get Rails up and running using a PostgreSQL database, and unfortunately I’m doing this on a machine I don’t administer directly. I can get Rails responding using the WEBrick server, and ‘hello, world’ pages work fine. However, after creating a database (on a seperate server) I can’t seem to get Rails speaking to it. At first, the Postgres gem wasn’t installed, but I had the sysadmin put that in. Now, though, I’m getting this error: Processing CraftController#new (for 141.161.18.159 at Wed Dec 07 14:32:38 PST 2005) Parameters: {“action”=\>“new”, “controller”=\>“craft”} NoMemoryError (failed to allocate memory): /usr/local/lib/ruby/gems/1.8/gems/postgres-pr-0.4.0/lib/buffer.rb:64:in `read' /usr/local/lib/ruby/gems/1.8/gems/postgres-pr-0.4.0/lib/buffer.rb:64:in`copy\_from\_stream’ /usr/local/lib/ruby/gems/1.8/gems/postgres-pr-0.4.0/lib/postgres-pr/message.rb:41:in `read' /usr/local/lib/ruby/gems/1.8/gems/postgres-pr-0.4.0/lib/postgres-pr/connection.rb:30:in`initialize’ /usr/local/lib/ruby/gems/1.8/gems/postgres-pr-0.4.0/lib/postgres-pr/connection.rb:29:in `loop' /usr/local/lib/ruby/gems/1.8/gems/postgres-pr-0.4.0/lib/postgres-pr/connection.rb:29:in`initialize’ /usr/local/lib/ruby/gems/1.8/gems/postgres-pr-0.4.0 /lib/postgres-pr/postgres-compat.rb:23:in `new' /usr/local/lib/ruby/gems/1.8/gems/postgres-pr-0.4.0 /lib/postgres-pr/postgres-compat.rb:23:in`initialize’ /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.11.1/lib/active\_record/connection\_adapters/postgresql\_adapter.rb:37:in `connect' /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.11.1/lib/active_record/connection_adapters/postgresql_adapter.rb:37:in`postgresql\_connection’ /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.11.1/lib/active\_record/query\_cache.rb:52:in `send' /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.11.1/lib/active_record/query_cache.rb:52:in`connection=’ /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.11.1/lib/active\_record/connection\_adapters/abstract\_adapter.rb:108:in `retrieve_connection' /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.11.1/lib/active_record/base.rb:239:in`connection’ /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.11.1/lib/active\_record/base.rb:246:in `connection' /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.11.1/lib/active_record/base.rb:1322:in`attributes\_from\_column\_definition’ /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.11.1/lib/active\_record/base.rb:928:in `initialize_without_callbacks' /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.11.1/lib/active_record/callbacks.rb:236:in`initialize’ /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.9.1/lib/action\_controller/scaffolding.rb:116:in `new' /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.9.1/lib/action_controller/scaffolding.rb:116:in`new’ /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.9.1/lib/action\_controller/base.rb:756:in `send' /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.9.1/lib/action_controller/base.rb:756:in`perform\_action\_without\_filters’ /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.9.1/lib/action\_controller/filters.rb:295:in `perform_action_without_benchmark' /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.9.1/lib/action_controller/benchmarking.rb:41:in`perform\_action\_without\_rescue’ /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.9.1/lib/action\_controller/benchmarking.rb:41:in `measure' /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.9.1/lib/action_controller/benchmarking.rb:41:in`perform\_action\_without\_rescue’ /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.9.1/lib/action\_controller/rescue.rb:80:in `perform_action' /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.9.1/lib/action_controller/base.rb:356:in`send’ /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.9.1/lib/action\_controller/base.rb:356:in `process' /usr/local/lib/ruby/gems/1.8/gems/rails-0.13.1/lib/dispatcher.rb:32:in`dispatch’ /usr/local/lib/ruby/gems/1.8/gems/rails-0.13.1/lib/webrick\_server.rb:105:in `handle_dispatch' /usr/local/lib/ruby/gems/1.8/gems/rails-0.13.1/lib/webrick_server.rb:71:in`service’ /usr/local/lib/ruby/1.8/webrick/httpserver.rb:104:in `service' /usr/local/lib/ruby/1.8/webrick/httpserver.rb:65:in`run’ /usr/local/lib/ruby/1.8/webrick/server.rb:155:in `start_thread' /usr/local/lib/ruby/1.8/webrick/server.rb:144:in`start’ /usr/local/lib/ruby/1.8/webrick/server.rb:144:in `start_thread' /usr/local/lib/ruby/1.8/webrick/server.rb:94:in`start’ /usr/local/lib/ruby/1.8/webrick/server.rb:89:in `each' /usr/local/lib/ruby/1.8/webrick/server.rb:89:in`start’ /usr/local/lib/ruby/1.8/webrick/server.rb:79:in `start' /usr/local/lib/ruby/1.8/webrick/server.rb:79:in`start’ /usr/local/lib/ruby/gems/1.8/gems/rails-0.13.1/lib/webrick\_server.rb:57:in `dispatch’ script/server:49 So, it looks like it’s something with memory, but… I can’t figure out what. Has anyone else run into this? I’m running against a 7.3 database, though, I’d heard Rails likes 8 and later, although, I’d also heard that had been fixed. Any help appreciated. Thanks, Colin F. ---
**Author:** ![colinfreas](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/43a26b/32.png) [@colinfreas](https://www.ruby-forum.com/u/colinfreas)\ **Post date:** [December 7, 2005, 11:53pm UTC](https://www.ruby-forum.com/t/rails-and-postgresql/49718/2 "2005-12-07T23:53:22Z")
What output do you get when you run “free” in a shell? ---
**Author:** ![colinfreas](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/43a26b/32.png) [@colinfreas](https://www.ruby-forum.com/u/colinfreas)\ **Post date:** [December 7, 2005, 11:53pm UTC](https://www.ruby-forum.com/t/rails-and-postgresql/49718/3 "2005-12-07T23:53:24Z")
On 12/7/05, Colin F. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > I’m trying to get Rails up and running using a PostgreSQL database, and > unfortunately I’m doing this on a machine I don’t administer directly. Rails-specific questions should go on the Rails mailing list. [http://lists.rubyonrails.org/mailman/listinfo/rails](http://lists.rubyonrails.org/mailman/listinfo/rails) ---
**Author:** ![colinfreas](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/43a26b/32.png) [@colinfreas](https://www.ruby-forum.com/u/colinfreas)\ **Post date:** [December 8, 2005, 6:47am UTC](https://www.ruby-forum.com/t/rails-and-postgresql/49718/4 "2005-12-08T06:47:37Z")
Roger that, Joe. Looks like my problem goes away using PostgreSQL 8, though, for anyone here who might run into the same problem. ---
**Author:** ![colinfreas](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/43a26b/32.png) [@colinfreas](https://www.ruby-forum.com/u/colinfreas)\ **Post date:** [December 8, 2005, 6:59am UTC](https://www.ruby-forum.com/t/rails-and-postgresql/49718/5 "2005-12-08T06:59:48Z")
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Dec 7, 2005, at 9:43 PM, Colin F. wrote: > Looks like my problem goes away using PostgreSQL 8, though, for > anyone here > who might run into the same problem. I’ve had better results with the C bindings as well: gem install postgres Best, jeremy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (Darwin) iD8DBQFDl8u7AQHALep9HFYRAjR+AJ9KunBM98iEDSaF/fQjQmxDvYfiqACfcOOe Ybdx0yy9c29ImiK4xXMYO3s= =uy07 -----END PGP SIGNATURE----- ---
**Author:** ![colinfreas](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/43a26b/32.png) [@colinfreas](https://www.ruby-forum.com/u/colinfreas)\ **Post date:** [December 8, 2005, 4:00pm UTC](https://www.ruby-forum.com/t/rails-and-postgresql/49718/6 "2005-12-08T16:00:37Z")
On Thu, 2005-12-08 at 14:59 +0900, Jeremy K. wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Dec 7, 2005, at 9:43 PM, Colin F. wrote: > > > Looks like my problem goes away using PostgreSQL 8, though, for > > anyone here > > who might run into the same problem. > > I’ve had better results with the C bindings as well: > gem install postgres Same here! Robby – /\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* - Robby R., Founder.Developer.Geek - PLANET ARGON, Rails Development, Consulting & Hosting - Portland, Oregon | p: 503.351.4730 | f: 815.642.4068 - [www.planetargon.com](http://www.planetargon.com) | [www.robbyonrails.com](http://www.robbyonrails.com) - Programming Rails | [www.programmingrails.com](http://www.programmingrails.com) \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*/