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

David Wheeler <david@kineticode.com>

From: "David E. Wheeler" <david@kineticode.com>

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

Cc: Josh Berkus <josh@agliodbs.com>, pgsql-hackers@postgresql.org

Date: 2011-03-01T21:15:24Z

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 →

Further refine patch for commenting operator implementation functions.
- 908ab8028640 9.1.0 cited
Fix citext's upgrade-from-unpackaged script to set its collation correctly.
- 94be9e3f0ca9 9.1.0 cited
Mark operator implementation functions as such in their comments.
- 94133a935414 9.1.0 cited
Add KNNGIST support to contrib/btree_gist.
- 8436489c81c2 9.1.0 cited
Fix plpython breakage detected on certain Fedora machines on buildfarm.
- 4c966d920fb7 9.1.0 cited

On Mar 1, 2011, at 1:12 PM, Tom Lane wrote:

> Collation, not correlation.  

Yeah, I'm fat-fingered today.

> 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

Ah, I remember now. That lead to this:

 http://archives.postgresql.org/pgsql-hackers/2011-02/msg01824.php

So it looks like what Peter said about updating the catalog is what needs to be done, and is simple, yes? But then pg_dump needs more collation-juju. Am I right?

Best,

David