Re: Alpha4 release blockers (was Re: wrapping up this CommitFest)

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: "David E. Wheeler" <david@kineticode.com>
Cc: Josh Berkus <josh@agliodbs.com>, pgsql-hackers@postgresql.org
Date: 2011-03-01T21:12:28Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Further refine patch for commenting operator implementation functions.

  2. Fix citext's upgrade-from-unpackaged script to set its collation correctly.

  3. Mark operator implementation functions as such in their comments.

  4. Add KNNGIST support to contrib/btree_gist.

  5. Fix plpython breakage detected on certain Fedora machines on buildfarm.

"David E. Wheeler" <david@kineticode.com> writes:
> On Mar 1, 2011, at 12:35 PM, Tom Lane wrote:
>> * Collation-related changes still needed in contrib/citext.  If we don't
>> have this done before alpha4, I'm afraid we'll have to generate a 1.1
>> update script to fix it for alpha4 users.  I'd just as soon not deal
>> with that overhead.

> What needs to happen here, exactly? I'm ignorant about about the correlation changes, but need to learn, and of course am willing to help out with citext, especially if correlation support might make it better.

Collation, not correlation.  The question is what collation property the
citext type needs to have, and how we get it to have that setting during
an upgrade from 9.0.  See
http://archives.postgresql.org/message-id/11548.1297983024@sss.pgh.pa.us

			regards, tom lane