Re: pg/postgres/CI

Michael Koziarski
Thu, 29 Jan 2009 20:27:01 -0000

> Koz and I discussed this on IRC.  I think his plan was to send an
> email to this list indicating plans to deprecate the postgres gem in a
> future version.  You just beat him to it :)

Indeed, this was basically the email I intended to send :)

> The current state is that
> geminstaller.yml only contains the pg gem, which imples that is the
> ''official'' one, even though the code which falls back to
postgres gem
> hasn''t been removed yet.
>
> I agree that there should be more sophistication to test other areas
> (are there others?) which do this "fallback" alternate gem
activation
> approach - untested code paths are bad.  Most of the work here will be
> in the rake test tasks, to ensure that the proper one is activated
> (via a flag, param, etc), then ci_build.rb can have multiple steps to
> test both scenarios.

It will also need some changes to the adapter to make sure that it
behaves consistently when you only have pg installed and run the tests
with postgres (or vice versa).

But fundamentally, I''m hoping some postgresql users can shed some
light on the situation.  There are two postgres gems, we''ll support
both for 2.3, but do we need to do that for 3.0?  Are there any
situations where you can''t just install pg?

--
Cheers

Koz