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

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>

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

Cc: "David E. Wheeler" <david@kineticode.com>, Josh Berkus <josh@agliodbs.com>, pgsql-hackers@postgresql.org

Date: 2011-03-06T05:16:20Z

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 Sat, Mar 5, 2011 at 5:28 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "David E. Wheeler" <david@kineticode.com> writes:
>> On Mar 4, 2011, at 7:44 PM, Robert Haas wrote:
>>> So it seems like the only thing that is an absolute must-do is write
>>> some release notes.
>
>> What about this?
>>> http://archives.postgresql.org/message-id/27152(dot)1299015062(at)sss(dot)pgh(dot)pa(dot)us
>
> Well, nobody else seems to be excited about it.  And it's not like there
> isn't a clear upgrade path if we decide to change CREATE TYPE later ---
> it'll just be a bit clunkier.

I am pretty suspicious that it's not a good design, but I don't
understand it well enough to propose a better one (if there is a
better one).

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company