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

Dave Page <dpage@pgadmin.org>

From: Dave Page <dpage@pgadmin.org>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Andrew Dunstan <andrew@dunslane.net>, Tom Lane <tgl@sss.pgh.pa.us>, Jan Urbański <wulczer@wulczer.org>, Robert Haas <robertmhaas@gmail.com>, Josh Berkus <josh@agliodbs.com>, pgsql-hackers <pgsql-hackers@postgresql.org>, David Fetter <david@fetter.org>
Date: 2011-03-02T19:16:13Z
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.

On Thu, Mar 3, 2011 at 12:42 AM, Alvaro Herrera
<alvherre@commandprompt.com> wrote:
> Excerpts from Andrew Dunstan's message of mié mar 02 14:02:30 -0300 2011:
>>
>> On 03/02/2011 11:49 AM, Tom Lane wrote:
>> > Well, we can eliminate that last theory, because there were both 32 and
>> > 64 bit buildfarm machines showing the crash, cf bobcat and crake.
>> > BTW, I see the former is now running F14, not F13 as claimed on the
>> > buildfarm dashboard,
>>
>>
>> That's because David apparently hasn't run update_personality.pl,
>> although he has in the past.
>
> Does this also explain that "moa" reports being GCC while it's actually
> Sun Studio?

moa has never changed - but there was a mixup with huia's keys when
they were first registered on the buildfarm. I wonder if it wasn't the
keys, but the rest of the info that was actually confused.

-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company