Comments on: PostgreSQL back-end for Ruby on Rails confusion http://blog.bigsmoke.us/2008/08/28/postgresql-back-end-for-ruby-on-rails-confusion Smokes your problems, coughs fresh air. Sat, 04 Feb 2012 20:03:14 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Rowan Rodrik http://blog.bigsmoke.us/2008/08/28/postgresql-back-end-for-ruby-on-rails-confusion#comment-88395 Rowan Rodrik Sat, 28 Nov 2009 18:55:14 +0000 http://blog.bigsmoke.us/?p=148#comment-88395 Turns out we were using the manually compiled <a href="http://rubyforge.org/projects/ruby-postgres/" rel="nofollow">version</a> in <tt>/usr/local</tt>. We noticed this while upgrading a very messy Debian testing to Debian Lenny. To recompile this version successfully against <tt>libpq-8.3</tt> instead of 8.2, I had to remove the <tt>#else</tt> clause from the following bit in <tt>postgres.c</tt> <code lang="c"> #ifndef HAVE_PG_ENCODING_TO_CHAR #define pg_encoding_to_char(x) "SQL_ASCII" #else extern char* pg_encoding_to_char(int); #endif </code> I got this patch from a forum post by one of the guys who forked this code, but we got none of these other projects to work with our version of ActiveRecord (the one in Rails 1.2.6). Turns out we were using the manually compiled version in /usr/local. We noticed this while upgrading a very messy Debian testing to Debian Lenny. To recompile this version successfully against libpq-8.3 instead of 8.2, I had to remove the #else clause from the following bit in postgres.c 

#ifndef HAVE_PG_ENCODING_TO_CHAR
#define pg_encoding_to_char(x) "SQL_ASCII"
#else
extern char* pg_encoding_to_char(int);
#endif

I got this patch from a forum post by one of the guys who forked this code, but we got none of these other projects to work with our version of ActiveRecord (the one in Rails 1.2.6).

]]> By: halfgaar http://blog.bigsmoke.us/2008/08/28/postgresql-back-end-for-ruby-on-rails-confusion#comment-80164 halfgaar Sun, 12 Jul 2009 08:38:11 +0000 http://blog.bigsmoke.us/?p=148#comment-80164 We don't. We only have one server... We don’t. We only have one server…

]]> By: Keith Basil http://blog.bigsmoke.us/2008/08/28/postgresql-back-end-for-ruby-on-rails-confusion#comment-80107 Keith Basil Fri, 10 Jul 2009 18:49:38 +0000 http://blog.bigsmoke.us/?p=148#comment-80107 How are you guys handling server replication and content synchronization with PostgreSQL? How are you guys handling server replication and content synchronization with PostgreSQL?

]]> By: Rowan Rodrik http://blog.bigsmoke.us/2008/08/28/postgresql-back-end-for-ruby-on-rails-confusion#comment-54310 Rowan Rodrik Tue, 02 Sep 2008 13:21:39 +0000 http://blog.bigsmoke.us/?p=148#comment-54310 O, the joy of documenting... I'm really glad we're getting into the habit of logging more of what we encounter. Who cares if it's of no use to the most of the rest of the world... I'd try to answer any of those questions, if only I could remember... O, the joy of documenting… I’m really glad we’re getting into the habit of logging more of what we encounter. Who cares if it’s of no use to the most of the rest of the world…

I’d try to answer any of those questions, if only I could remember…

]]> By: halfgaar http://blog.bigsmoke.us/2008/08/28/postgresql-back-end-for-ruby-on-rails-confusion#comment-51213 halfgaar Thu, 28 Aug 2008 14:02:41 +0000 http://blog.bigsmoke.us/?p=148#comment-51213 Bigsmoke, if you have anything to add, please do... Bigsmoke, if you have anything to add, please do…

]]>