Horton

Re: Draft release notes complete

Alvaro Herrera <alvherre@2ndquadrant.com>

View thread
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: Magnus Hagander <magnus@hagander.net>, Andrew Dunstan <andrew@dunslane.net>, Peter Eisentraut <peter_e@gmx.net>, Tom Lane <tgl@sss.pgh.pa.us>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2012-08-30T02:23:31Z
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. Expose track_iotiming information via pg_stat_statements.

  2. Rewrite GiST support code for rangetypes.

  3. Clean up a couple of box gist helper functions.

  4. Replace the "New Linear" GiST split algorithm for boxes and points with a

Excerpts from Bruce Momjian's message of mié ago 29 21:25:11 -0400 2012:
> On Thu, May 31, 2012 at 05:58:58PM +0200, Magnus Hagander wrote:
> > On Thu, May 31, 2012 at 5:55 PM, Bruce Momjian <bruce@momjian.us> wrote:
> > > On Tue, May 15, 2012 at 12:57:37PM -0400, Magnus Hagander wrote:
> > >> On Fri, May 11, 2012 at 11:44 AM, Andrew Dunstan <andrew@dunslane.net> wrote:

> > >> > If it's of any use to you I have made some adjustments to the buildfarm code
> > >> > which would let you do *just* the docs build (and dist make if you want). It
> > >> > would still pull from git, and only do anything if there's a (relevant)
> > >> > change. So using that to set up a machine that would run every few minutes
> > >> > might work. Of course, building the docs can itself be fairly compute
> > >> > intensive, so you still might not want to run every few minutes if that's a
> > >> > limiting factor.
> > >>
> > >> that would definitely be useful. Compute intensive is not really a
> > >> problem, we can easily shape the box on that (and I think we already
> > >> do).
> > >>
> > >> Do you have some details of what to do and how to do it to use that,
> > >> so Stefan can set it up for us ? ;)
> > >
> > > Where are we on building the development docs more frequently?
> > 
> > Still waiting for details on how it works to set that up on the
> > buildfarm client.
> 
> Where are we on this?

Waiting on Andrew.

As far as I can see, we need to update the machine to release 4.7, and
then install a "skip file" or something like that.  Andrew, can you
please explain how is that to be used?  I don't see it documented
anywhere.

Please note that we have cron jobs that run every branch (we use
run_build.pl for each branch separately, not run_branches.pl) and a
signle build-farm.conf.  It would be good if we could continue to use a
single config file for all builds, including a build that *only* does
the docs.  If we can have a second file that only #includes the other
one somehow and just tweaks %skip_step, that would work.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services