Skip to content

Commit 1895441

Browse files
committed
Document possible issues when a precompiled pg gem is used (Fixes #60)
1 parent 8497009 commit 1895441

File tree

1 file changed

+14
-1
lines changed

1 file changed

+14
-1
lines changed

README.rdoc

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -127,13 +127,26 @@ requirements:
127127
PostgreSQL defaulting to ISO, Sequel also manually sets the
128128
date format to ISO by default, so unless you are overriding that
129129
setting (via DB.use_iso_date_format = false), you should be OK.
130+
130131
* Adding your own type conversion procs only has an effect if those
131132
types are not handled by default.
133+
132134
* You do not need to require the library, the sequel postgres adapter
133135
will require it automatically. If you are using bundler, you
134136
should add it to your Gemfile like so:
135137

136-
gem 'sequel_pg', :require=>'sequel'
138+
gem 'sequel_pg', require: 'sequel'
139+
140+
* Using a precompiled pg gem can cause issues in certain cases,
141+
since it statically links a libpq that could differ from the system
142+
libpq dynamically linked to the sequel_pg gem. You can work around
143+
the issue by forcing the ruby platform for the pg gem:
144+
145+
# Manual install
146+
gem install pg --platform ruby
147+
148+
# Gemfile
149+
gem 'pg', force_ruby_platform: true
137150

138151
* sequel_pg currently calls functions defined in the pg gem, which
139152
does not work on Windows and does not work in some unix-like

0 commit comments

Comments
 (0)