Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
A git mirror of the 'pg' gem.
C Ruby Diff C++
Failed to load latest commit information.
ext Avoid possible symbol name clash when linking againt static libpq.
lib Allow URI connection string
misc Update windows cross compilation tasks to the latest Openssl+Postgres…
sample Whitespace cleanup
spec Merge from git branch.
.gemtest Converted to Hoe
.hgignore Add generated error codes file to the ignorelist
.hgsigs Added signature for changeset ba5aff64b5cb
.hgtags Added tag v0.18.1 for changeset f97dd6cb4f34
.hoerc Add the Gemfile to the list of files that don't have to be on the Man…
.irbrc Rearranging classes under the PG namespace to be a better Ruby citizen
.pryrc Rearranging classes under the PG namespace to be a better Ruby citizen
.rvm.gems Convert specs to expect syntax for RSpec 3
.rvmrc Test under Ruby 2.0.0 by default
.tm_properties Fix indent in project settings
.travis.yml Update ruby and postgresql versions for travic-ci
BSDL Add missing BSDL license file (fixes #108)
Contributors.rdoc Update Rafał Bigaj's email address in Contributors.rdoc at his request
Gemfile Update Gemfile
History.rdoc Fix decoding of fractional timezones like "04:30".
LICENSE Updated/simplified authors/license sections of the README, API doc cl…
Manifest.txt Keep the manifest sorted so it can be diffed.
POSTGRES fix cross compilation of win32 binary gem, fix mixed case file naming
README-OS_X.rdoc More case-corrections
README-Windows.rdoc More case-corrections
README.ja.rdoc Update READMEs
README.rdoc Update copyright notices
Rakefile Fix the minimum Ruby version (closes #199)
Rakefile.cross gcc option -static-libgcc is required for i386-mingw32 build.







Pg is the Ruby interface to the PostgreSQL RDBMS.

It works with PostgreSQL 8.4 and later.

A small example usage:

#!/usr/bin/env ruby

require 'pg'

# Output a table of current connections to the DB
conn = PG.connect( dbname: 'sales' )
conn.exec( "SELECT * FROM pg_stat_activity" ) do |result|
  puts "     PID | User             | Query"
result.each do |row|
    puts " %7d | %-16s | %s " %
      row.values_at('procpid', 'usename', 'current_query')

Build Status



  • Ruby 1.9.3-p392, or 2.0.0-p0.

  • PostgreSQL 8.4.x or later (with headers, -dev packages, etc).

It may work with earlier versions of Ruby/PostgreSQL as well, but those are not regularly tested.

How To Install

Install via RubyGems:

gem install pg

You may need to specify the path to the 'pg_config' program installed with Postgres:

gem install pg -- --with-pg-config=<path to pg_config>

If you're installing via Bundler, you can provide compile hints like so:

bundle config --with-pg-config=<path to pg_config>

See README-OS_X.rdoc for more information about installing under MacOS X, and README-Windows.rdoc for Windows build/installation instructions.

There's also a Google+ group and a mailing list if you get stuck, or just want to chat about something.

Type Casts

Pg can optionally type cast result values and query parameters in Ruby or native C code. This can speed up data transfers to and from the database, because String allocations are reduced and conversions in (slower) Ruby code can be omitted.

Very basic type casting can be enabled by:

conn.type_map_for_results = conn
# ... this works for result value mapping:
conn.exec("select 1, now(), '{2,3}'::int[]").values
    # => [[1, 2014-09-21 20:51:56 +0200, [2, 3]]]

conn.type_map_for_queries = conn
# ... and this for param value mapping:
conn.exec_params("SELECT $1::text, $2::text, $3::text", [1, 1.23, [2,3]]).values
    # => [["1", "1.2300000000000000E+00", "{2,3}"]]

But Pg's type casting is highly customizable. That's why it's divided into 2 layers:

Encoders / Decoders (ext/pg_*coder.c, lib/pg/*coder.rb)

This is the lower layer, containing encoding classes that convert Ruby objects for transmission to the DBMS and decoding classes to convert received data back to Ruby objects. The classes are namespaced according to their format and direction in PG::TextEncoder, PG::TextDecoder, PG::BinaryEncoder and PG::BinaryDecoder.

It is possible to assign a type OID, format code (text or binary) and optionally a name to an encoder or decoder object. It's also possible to build composite types by assigning an element encoder/decoder. PG::Coder objects can be used to set up a PG::TypeMap or alternatively to convert single values to/from their string representation.

PG::TypeMap and derivations (ext/pg_type_map*.c, lib/pg/type_map*.rb)

A TypeMap defines which value will be converted by which encoder/decoder. There are different type map strategies, implemented by several derivations of this class. They can be chosen and configured according to the particular needs for type casting. The default type map is PG::TypeMapAllStrings.

A type map can be assigned per connection or per query respectively per result set. Type maps can also be used for COPY in and out data streaming.


To report bugs, suggest features, or check out the source with Mercurial, check out the project page. If you prefer Git, there's also a Github mirror.

After checking out the source, run:

$ rake newb

This task will install any missing dependencies, run the tests/specs, and generate the API documentation.

The current maintainers are Michael Granger <> and Lars Kanis <>.


Copyright © 1997-2015 by the authors.

  • Jeff Davis <>

  • Guy Decoux (ts) <>

  • Michael Granger <>

  • Lars Kanis <>

  • Dave Lee

  • Eiji Matsumoto <>

  • Yukihiro Matsumoto <>

  • Noboru Saitou <>

You may redistribute this software under the same terms as Ruby itself; see or the LICENSE file in the source for details.

Portions of the code are from the PostgreSQL project, and are distributed under the terms of the PostgreSQL license, included in the file POSTGRES.

Portions copyright LAIKA, Inc.


See Contributors.rdoc for the many additional fine people that have contributed to this library over the years.

We are thankful to the people at the ruby-list and ruby-dev mailing lists. And to the people who developed PostgreSQL.

Something went wrong with that request. Please try again.