From: mathew <meta@...>
Date: 2011-01-22T03:15:53+09:00
Subject: [ruby-core:34761] Re: [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?

On Fri, Jan 21, 2011 at 10:11, Zeno Davatz <redmine@ruby-lang.org> wrote:
> 2. pg does not work with Ruby 1.9.2 because of some PGconn error that
> we could not track down yet even though we tried all afternoon.
> PGconn is called by dbd-pg (0.3.9) but there we need to continue
> later: http://url.ba/hgwg

I would suggest that you
(a) start a new ticket for this apparent pg gem problem, and
(b) dump the actual SQL which is being sent to PostgreSQL, so the rest
of us can attempt to reproduce the problem.

The definition of the relevant table(s) would also be helpful.

My suspicion from the error message is that it's not actually pg or
Ruby at fault, but something else is trying to create an index which
already exists--either because it's failing to detect that the index
exists, or because it's creating a temporary index and then failing to
remove it.

If you can get me some actual SQL which fails when passed to pg in
1.9.2 but works when passed to pg in 1.9.1, I'll be glad to try and
reproduce the problem.


mathew