Horton

Re: Draft release notes complete

Bruce Momjian <bruce@momjian.us>

View thread
From: Bruce Momjian <bruce@momjian.us>
To: Magnus Hagander <magnus@hagander.net>
Cc: Andrew Dunstan <andrew@dunslane.net>, Peter Eisentraut <peter_e@gmx.net>, Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2012-05-31T15:55:18Z
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

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:
> >
> >
> > On 05/11/2012 05:32 AM, Magnus Hagander wrote:
> >>
> >>
> >> But in the interest of actually being productive - what *is* the
> >> usecase for needing a 5 minute turnaround time? I don't buy the "check
> >> what a patch looks like", because that should be done *before* the
> >> commit, not after - so it's best verified by a local docs build anyway
> >> (which will also be faster).
> >>
> >> I'm sure we can put something in with a pretty quick turnaround again
> >> without too much strain on the system, but it does, as I mentioned
> >> before, require decoupling it from the buildfarm which means it's not
> >> just tweaking a config file.
> >
> >
> > 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?

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +