Horton

Re: Draft release notes complete

Bruce Momjian <bruce@momjian.us>

View thread
From: Bruce Momjian <bruce@momjian.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Magnus Hagander <magnus@hagander.net>, Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2012-05-10T15:54:34Z
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 Thu, May 10, 2012 at 11:46:20AM -0400, Andrew Dunstan wrote:
> >>I don't think 5 minutes is anywhere near necessary even for the docs,
> >>but there is a lot of room between 5 minutes and 4 hours, so we can
> >>definitely shorten it.
> >Do you want me to just setup a build on my machine like we did before;
> >5 minutes is no problem for me.
> >
> >I use the doc build to show patch submitters what their final work looks
> >like, and anything more than a few minutes delay makes that useless.
> >
> 
> It's been done the current way for quite a few months now. If you're
> only noticing it now is it really such an inconvenience? Having said
> that, I'm not at all opposed to reducing the lag time.

Well, I am not applying doc patches much anymore;  my point is that the
first time I actually need to send out a URL of the docs, it wasn't
sufficient for me.

Yes, I can work around it, but it that what we want everyone to do?  I
don't remember this change being discussed anywhere I see.

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

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