pg 1.3.0.rc2-x64-mingw-ucrt

data/Manifest.txt

@@ -0,0 +1,72 @@
+.gemtest
+BSDL
+Contributors.rdoc
+History.rdoc
+LICENSE
+Manifest.txt
+POSTGRES
+README-OS_X.rdoc
+README-Windows.rdoc
+README.ja.rdoc
+README.rdoc
+Rakefile
+Rakefile.cross
+ext/errorcodes.def
+ext/errorcodes.rb
+ext/errorcodes.txt
+ext/extconf.rb
+ext/gvl_wrappers.c
+ext/gvl_wrappers.h
+ext/pg.c
+ext/pg.h
+ext/pg_binary_decoder.c
+ext/pg_binary_encoder.c
+ext/pg_coder.c
+ext/pg_connection.c
+ext/pg_copy_coder.c
+ext/pg_errors.c
+ext/pg_record_coder.c
+ext/pg_result.c
+ext/pg_text_decoder.c
+ext/pg_text_encoder.c
+ext/pg_tuple.c
+ext/pg_type_map.c
+ext/pg_type_map_all_strings.c
+ext/pg_type_map_by_class.c
+ext/pg_type_map_by_column.c
+ext/pg_type_map_by_mri_type.c
+ext/pg_type_map_by_oid.c
+ext/pg_type_map_in_ruby.c
+ext/pg_util.c
+ext/pg_util.h
+ext/vc/pg.sln
+ext/vc/pg_18/pg.vcproj
+ext/vc/pg_19/pg_19.vcproj
+lib/pg.rb
+lib/pg/basic_type_mapping.rb
+lib/pg/binary_decoder.rb
+lib/pg/coder.rb
+lib/pg/connection.rb
+lib/pg/constants.rb
+lib/pg/exceptions.rb
+lib/pg/result.rb
+lib/pg/text_decoder.rb
+lib/pg/text_encoder.rb
+lib/pg/tuple.rb
+lib/pg/type_map_by_column.rb
+spec/data/expected_trace.out
+spec/data/random_binary_data
+spec/helpers.rb
+spec/pg/basic_type_mapping_spec.rb
+spec/pg/connection_spec.rb
+spec/pg/connection_sync_spec.rb
+spec/pg/result_spec.rb
+spec/pg/tuple_spec.rb
+spec/pg/type_map_by_class_spec.rb
+spec/pg/type_map_by_column_spec.rb
+spec/pg/type_map_by_mri_type_spec.rb
+spec/pg/type_map_by_oid_spec.rb
+spec/pg/type_map_in_ruby_spec.rb
+spec/pg/type_map_spec.rb
+spec/pg/type_spec.rb
+spec/pg_spec.rb

data/POSTGRES

@@ -0,0 +1,23 @@
+PostgreSQL Database Management System
+(formerly known as Postgres, then as Postgres95)
+
+Portions Copyright (c) 1996-2008, PostgreSQL Global Development Group
+
+Portions Copyright (c) 1994, The Regents of the University of California
+
+Permission to use, copy, modify, and distribute this software and its
+documentation for any purpose, without fee, and without a written agreement
+is hereby granted, provided that the above copyright notice and this
+paragraph and the following two paragraphs appear in all copies.
+
+IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR
+DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING
+LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS
+DOCUMENTATION, EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGE.
+
+THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES,
+INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
+AND FITNESS FOR A PARTICULAR PURPOSE.  THE SOFTWARE PROVIDED HEREUNDER IS
+ON AN "AS IS" BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO
+PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.

data/README-OS_X.rdoc

@@ -0,0 +1,68 @@
+= Compiling on MacOS X
+
+The EnterpriseDB packages are the recommended PostgreSQL installations to use
+with MacOS X. They eliminate most or all of the issues with getting 'pg'
+installed, linked correctly, and running.
+
+== Segfaults and SSL Support
+
+If you need a custom installation of PostgreSQL, you should ensure that you
+either compile it against the same version of OpenSSL as the OpenSSL extension
+of the Ruby you'll be using, or compile it without SSL support. If you fail to
+do this, you will likely see segfaults when you use 'pg' and the 'openssl'
+extension at the same time. You can see what library it's linked against using
+'otool -L'; for example, on my 10.7 machine I use for 'pg' development:
+
+    $ otool -L /System/Library/Frameworks/Ruby.framework/Versions\
+      /1.8/usr/lib/ruby/1.8/universal-darwin11.0/openssl.bundle
+
+    /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/\
+        lib/ruby/1.8/universal-darwin11.0/openssl.bundle:
+        /System/Library/Frameworks/Ruby.framework/Versions/1.8/\
+            usr/lib/libruby.1.dylib (compatibility version 1.8.0, \
+            current version 1.8.7)
+        /usr/lib/libssl.0.9.8.dylib (compatibility version 0.9.8, \
+            current version 0.9.8)
+        /usr/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, \
+            current version 0.9.8)
+        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, \
+            current version 159.0.0)
+
+
+== Dealing with Installation Problems
+
+If you are building/installing pg on MacOS X, and the installation doesn't
+work at first, here are a few things you can try.
+
+=== pg_config
+
+The first thing you should do is ensure that the 'pg_config' tool that comes
+with Postgres is in your path. If it isn't, or the one that's first in your
+path isn't the one that was installed with the Postgres you want to build
+against, you can specify the path to it with the --with-pg-config option.
+
+For example, if you're using the Ruby binary that comes with OSX, and
+PostgreSQL 9.0.x installed from MacPorts, do:
+
+	gem install -- --with-pg-config=/opt/local/lib/postgresql90/bin/pg_config
+
+=== ARCHFLAGS and Universal Binaries
+
+OS X supports both architecture-specific binaries (e.g. i386), as well as
+universal binaries (i.e. i386 & ppc). If Ruby is built as a universal binary
+and PostgreSQL is not, you need to specify the path to the appropriate
+pg_config binary or set the environment variable ARCHFLAGS appropriately.
+
+Alternatively, if the build system can't figure out which architectures it
+should include, you may need to set the 'ARCHFLAGS' environment variable
+explicitly:
+
+	sudo env ARCHFLAGS='-arch x86_64' gem install pg
+
+or, if you're building from source:
+
+	rake compile ARCHFLAGS="-arch x86_64"
+
+Note that the recommended EnterpriseDB packages are correctly compiled as
+universal binaries, and don't need any of these workarounds.
+

data/README-Windows.rdoc

@@ -0,0 +1,56 @@
+= Compiling 'pg' on MS Windows
+
+In order to build this extension on MS Windows you will need a couple things.
+
+First, a compiler. For the one click installer this means you should use
+the DevKit or the compiler that comes with cygwin if you're building on that
+platform.
+
+If you've built Ruby yourself, you should use the same compiler to build
+this library that you used to build Ruby.
+
+Second, PostgreSQL. Be sure you installed it with the development header
+files if you installed it using the standard PostgreSQL installer for
+Windows. If you didn't, you can run the installer again, select "modify",
+and then select the 'development headers' option to install them.
+
+I recommend making sure that 'pg_config.exe' is in your PATH. The PostgreSQL
+installer for Windows does not necessarily update your PATH when it installs
+itself, so you may need to do this manually. This isn't strictly necessary,
+however.
+
+In order to build ruby-pg, just run 'rake'. If the pg_config.exe executable
+is not in your PATH, you'll need to explicitly point ruby-pg to where your
+PostgreSQL headers and libraries are with something like this:
+
+	rake --with-pg-dir=c:/progra~1/postgr~1/8.3
+
+Adjust your path accordingly. BE SURE TO USE THE SHORT PATH NAMES! If you
+try to use a path with spaces in it, the nmake.exe program will choke.
+
+
+== Building binary 'pg' gems for MS Windows
+
+Binary gems for windows can be built on Linux, OS-X and even on Windows
+with the help of docker. This is how regular windows gems are built for
+rubygems.org .
+
+To do this, install boot2docker {on Windows}[https://github.com/boot2docker/windows-installer/releases]
+or {on OS X}[https://github.com/boot2docker/osx-installer/releases] and make
+sure it is started. A native Docker installation is best on Linux.
+
+Then run:
+
+	rake gem:windows
+
+This will download a docker image suited for building windows gems, and it
+will download and build OpenSSL and PostgreSQL. Finally the gem is built
+containing binaries for all supported ruby versions.
+
+
+== Reporting Problems
+
+If you have any problems you can submit them via {the project's
+issue-tracker}[https://github.com/ged/ruby-pg/issues]. And submit questions, problems, or
+solutions, so that it can be improved.
+

data/README.ja.rdoc

@@ -0,0 +1,13 @@
+= pg
+
+home :: https://github.com/ged/ruby-pg
+docs :: http://deveiate.org/code/pg
+
+
+== Description
+
+This file needs a translation of the English README. Pull requests, patches, or
+volunteers gladly accepted.
+
+Until such time, please accept my sincere apologies for not knowing Japanese.
+

data/README.rdoc

@@ -0,0 +1,214 @@
+= pg
+
+home :: https://github.com/ged/ruby-pg
+docs :: http://deveiate.org/code/pg
+clog :: link:/History.rdoc
+
+{<img src="https://badges.gitter.im/Join%20Chat.svg" alt="Join the chat at https://gitter.im/ged/ruby-pg">}[https://gitter.im/ged/ruby-pg?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge]
+
+
+== Description
+
+Pg is the Ruby interface to the {PostgreSQL RDBMS}[http://www.postgresql.org/].
+
+It works with {PostgreSQL 9.3 and later}[http://www.postgresql.org/support/versioning/].
+
+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('pid', 'usename', 'query')
+    end
+  end
+
+== Build Status
+
+{<img src="https://github.com/ged/ruby-pg/actions/workflows/source-gem.yml/badge.svg?branch=master" alt="Build Status Github Actions" />}[https://github.com/ged/ruby-pg/actions/workflows/source-gem.yml]
+{<img src="https://ci.appveyor.com/api/projects/status/gjx5axouf3b1wicp?svg=true" alt="Build Status Appveyor" />}[https://ci.appveyor.com/project/ged/ruby-pg-9j8l3]
+{<img src="https://app.travis-ci.com/larskanis/ruby-pg.svg?branch=master" alt="Build Status" />}[https://app.travis-ci.com/larskanis/ruby-pg]
+
+== Requirements
+
+* Ruby 2.4 or newer
+* PostgreSQL 9.3.x or later (with headers, -dev packages, etc).
+
+It usually works with earlier versions of Ruby/PostgreSQL as well, but those are
+not regularly tested.
+
+
+== Versioning
+
+We tag and release gems according to the {Semantic Versioning}[http://semver.org/] principle.
+
+As a result of this policy, you can (and should) specify a dependency on this gem using the {Pessimistic Version Constraint}[http://guides.rubygems.org/patterns/#pessimistic-version-constraint] with two digits of precision.
+
+For example:
+
+  spec.add_dependency 'pg', '~> 1.0'
+
+
+== 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 build.pg --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}[http://goo.gl/TFy1U] and a
+{mailing list}[http://groups.google.com/group/ruby-pg] if you get stuck, or just
+want to chat about something.
+
+If you want to install as a signed gem, the public certs of the gem signers
+can be found in {the `certs` directory}[https://github.com/ged/ruby-pg/tree/master/certs]
+of the repository.
+
+
+== 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 = PG::BasicTypeMapForResults.new 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 = PG::BasicTypeMapForQueries.new 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.
+
+The following PostgreSQL column types are supported by ruby-pg (TE = Text Encoder, TD = Text Decoder, BE = Binary Encoder, BD = Binary Decoder):
+* Integer: {TE}[rdoc-ref:PG::TextEncoder::Integer], {TD}[rdoc-ref:PG::TextDecoder::Integer], {BD}[rdoc-ref:PG::BinaryDecoder::Integer] 💡 No links? Switch to {here}[https://deveiate.org/code/pg/README_rdoc.html#label-Type+Casts] 💡
+  * BE: {Int2}[rdoc-ref:PG::BinaryEncoder::Int2], {Int4}[rdoc-ref:PG::BinaryEncoder::Int4], {Int8}[rdoc-ref:PG::BinaryEncoder::Int8]
+* Float: {TE}[rdoc-ref:PG::TextEncoder::Float], {TD}[rdoc-ref:PG::TextDecoder::Float], {BD}[rdoc-ref:PG::BinaryDecoder::Float]
+* Numeric: {TE}[rdoc-ref:PG::TextEncoder::Numeric], {TD}[rdoc-ref:PG::TextDecoder::Numeric]
+* Boolean: {TE}[rdoc-ref:PG::TextEncoder::Boolean], {TD}[rdoc-ref:PG::TextDecoder::Boolean], {BE}[rdoc-ref:PG::BinaryEncoder::Boolean], {BD}[rdoc-ref:PG::BinaryDecoder::Boolean]
+* String: {TE}[rdoc-ref:PG::TextEncoder::String], {TD}[rdoc-ref:PG::TextDecoder::String], {BE}[rdoc-ref:PG::BinaryEncoder::String], {BD}[rdoc-ref:PG::BinaryDecoder::String]
+* Bytea: {TE}[rdoc-ref:PG::TextEncoder::Bytea], {TD}[rdoc-ref:PG::TextDecoder::Bytea], {BE}[rdoc-ref:PG::BinaryEncoder::Bytea], {BD}[rdoc-ref:PG::BinaryDecoder::Bytea]
+* Base64: {TE}[rdoc-ref:PG::TextEncoder::ToBase64], {TD}[rdoc-ref:PG::TextDecoder::FromBase64], {BE}[rdoc-ref:PG::BinaryEncoder::FromBase64], {BD}[rdoc-ref:PG::BinaryDecoder::ToBase64]
+* Timestamp:
+  * TE: {local}[rdoc-ref:PG::TextEncoder::TimestampWithoutTimeZone], {UTC}[rdoc-ref:PG::TextEncoder::TimestampUtc], {with-TZ}[rdoc-ref:PG::TextEncoder::TimestampWithTimeZone]
+  * TD: {local}[rdoc-ref:PG::TextDecoder::TimestampLocal], {UTC}[rdoc-ref:PG::TextDecoder::TimestampUtc], {UTC-to-local}[rdoc-ref:PG::TextDecoder::TimestampUtcToLocal]
+  * BD: {local}[rdoc-ref:PG::BinaryDecoder::TimestampLocal], {UTC}[rdoc-ref:PG::BinaryDecoder::TimestampUtc], {UTC-to-local}[rdoc-ref:PG::BinaryDecoder::TimestampUtcToLocal]
+* Date: {TE}[rdoc-ref:PG::TextEncoder::Date], {TD}[rdoc-ref:PG::TextDecoder::Date]
+* JSON and JSONB: {TE}[rdoc-ref:PG::TextEncoder::JSON], {TD}[rdoc-ref:PG::TextDecoder::JSON]
+* Inet: {TE}[rdoc-ref:PG::TextEncoder::Inet], {TD}[rdoc-ref:PG::TextDecoder::Inet]
+* Array: {TE}[rdoc-ref:PG::TextEncoder::Array], {TD}[rdoc-ref:PG::TextDecoder::Array]
+* Composite Type (also called "Row" or "Record"): {TE}[rdoc-ref:PG::TextEncoder::Record], {TD}[rdoc-ref:PG::TextDecoder::Record]
+
+The following text formats can also be encoded although they are not used as column type:
+* COPY input and output data: {TE}[rdoc-ref:PG::TextEncoder::CopyRow], {TD}[rdoc-ref:PG::TextDecoder::CopyRow]
+* Literal for insertion into SQL string: {TE}[rdoc-ref:PG::TextEncoder::QuotedLiteral]
+* SQL-Identifier: {TE}[rdoc-ref:PG::TextEncoder::Identifier], {TD}[rdoc-ref:PG::TextDecoder::Identifier]
+
+=== 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.
+See PG::Connection#copy_data .
+
+The following base type maps are available:
+* PG::TypeMapAllStrings - encodes and decodes all values to and from strings (default)
+* PG::TypeMapByClass - selects encoder based on the class of the value to be sent
+* PG::TypeMapByColumn - selects encoder and decoder by column order
+* PG::TypeMapByOid - selects decoder by PostgreSQL type OID
+* PG::TypeMapInRuby - define a custom type map in ruby
+
+The following type maps are prefilled with type mappings from the PG::BasicTypeRegistry :
+* PG::BasicTypeMapForResults - a PG::TypeMapByOid prefilled with decoders for common PostgreSQL column types
+* PG::BasicTypeMapBasedOnResult - a PG::TypeMapByOid prefilled with encoders for common PostgreSQL column types
+* PG::BasicTypeMapForQueries - a PG::TypeMapByClass prefilled with encoders for common Ruby value classes
+
+
+== Contributing
+
+To report bugs, suggest features, or check out the source with Git,
+{check out the project page}[https://github.com/ged/ruby-pg].
+
+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 <ged@FaerieMUD.org> and
+Lars Kanis <lars@greiz-reinsdorf.de>.
+
+
+== Copying
+
+Copyright (c) 1997-2019 by the authors.
+
+* Jeff Davis <ruby-pg@j-davis.com>
+* Guy Decoux (ts) <decoux@moulon.inra.fr>
+* Michael Granger <ged@FaerieMUD.org>
+* Lars Kanis <lars@greiz-reinsdorf.de>
+* Dave Lee
+* Eiji Matsumoto <usagi@ruby.club.or.jp>
+* Yukihiro Matsumoto <matz@ruby-lang.org>
+* Noboru Saitou <noborus@netlab.jp>
+
+You may redistribute this software under the same terms as Ruby itself; see
+https://www.ruby-lang.org/en/about/license.txt or the BSDL 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.
+
+
+== Acknowledgments
+
+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.

data/Rakefile

@@ -0,0 +1,106 @@
+# -*- rake -*-
+
+require 'rbconfig'
+require 'pathname'
+require 'tmpdir'
+require 'rake/extensiontask'
+require 'rake/clean'
+require 'rspec/core/rake_task'
+require 'bundler'
+require 'bundler/gem_helper'
+
+# Build directory constants
+BASEDIR = Pathname( __FILE__ ).dirname
+SPECDIR = BASEDIR + 'spec'
+LIBDIR  = BASEDIR + 'lib'
+EXTDIR  = BASEDIR + 'ext'
+PKGDIR  = BASEDIR + 'pkg'
+TMPDIR  = BASEDIR + 'tmp'
+TESTDIR = BASEDIR + "tmp_test_specs"
+
+DLEXT   = RbConfig::CONFIG['DLEXT']
+EXT     = LIBDIR + "pg_ext.#{DLEXT}"
+
+GEMSPEC = 'pg.gemspec'
+
+CLOBBER.include( TESTDIR.to_s )
+CLEAN.include( PKGDIR.to_s, TMPDIR.to_s )
+CLEAN.include "lib/*/libpq.dll"
+CLEAN.include "lib/pg_ext.*"
+CLEAN.include "lib/pg/postgresql_lib_path.rb"
+
+load 'Rakefile.cross'
+
+Bundler::GemHelper.install_tasks
+$gem_spec = Bundler.load_gemspec(GEMSPEC)
+
+desc "Turn on warnings and debugging in the build."
+task :maint do
+	ENV['MAINTAINER_MODE'] = 'yes'
+end
+
+# Rake-compiler task
+Rake::ExtensionTask.new do |ext|
+	ext.name           = 'pg_ext'
+	ext.gem_spec       = $gem_spec
+	ext.ext_dir        = 'ext'
+	ext.lib_dir        = 'lib'
+	ext.source_pattern = "*.{c,h}"
+	ext.cross_compile  = true
+	ext.cross_platform = CrossLibraries.map(&:for_platform)
+
+	ext.cross_config_options += CrossLibraries.map do |lib|
+		{
+			lib.for_platform => [
+				"--enable-windows-cross",
+				"--with-pg-include=#{lib.static_postgresql_incdir}",
+				"--with-pg-lib=#{lib.static_postgresql_libdir}",
+				# libpq-fe.h resides in src/interfaces/libpq/ before make install
+				"--with-opt-include=#{lib.static_postgresql_libdir}",
+			]
+		}
+	end
+
+	# Add libpq.dll to windows binary gemspec
+	ext.cross_compiling do |spec|
+		spec.files << "lib/#{spec.platform}/libpq.dll"
+	end
+end
+
+RSpec::Core::RakeTask.new(:spec).rspec_opts = "--profile -cfdoc"
+task :test => :spec
+
+# Use the fivefish formatter for docs generated from development checkout
+require 'rdoc/task'
+
+RDoc::Task.new( 'docs' ) do |rdoc|
+	rdoc.main = "README.rdoc"
+	rdoc.rdoc_files.include( "*.rdoc", "lib/**/*.rb", 'ext/**/*.{c,h}' )
+	rdoc.generator = :fivefish
+	rdoc.title = "PG: The Ruby PostgreSQL Driver"
+	rdoc.rdoc_dir = 'doc'
+end
+
+desc "Build the source gem #{$gem_spec.full_name}.gem into the pkg directory"
+task :gem => :build
+
+task :clobber do
+	puts "Stop any Postmaster instances that remain after testing."
+	require_relative 'spec/helpers'
+	PG::TestingHelpers.stop_existing_postmasters()
+end
+
+desc "Update list of server error codes"
+task :update_error_codes do
+	URL_ERRORCODES_TXT = "http://git.postgresql.org/gitweb/?p=postgresql.git;a=blob_plain;f=src/backend/utils/errcodes.txt;hb=refs/tags/REL_14_0"
+
+	ERRORCODES_TXT = "ext/errorcodes.txt"
+	sh "wget #{URL_ERRORCODES_TXT.inspect} -O #{ERRORCODES_TXT.inspect} || curl #{URL_ERRORCODES_TXT.inspect} -o #{ERRORCODES_TXT.inspect}"
+
+	ruby 'ext/errorcodes.rb', 'ext/errorcodes.txt', 'ext/errorcodes.def'
+end
+
+file 'ext/pg_errors.c' => ['ext/errorcodes.def'] do
+	# trigger compilation of changed errorcodes.def
+	touch 'ext/pg_errors.c'
+end