Horton

Re: Draft release notes complete

Bruce Momjian <bruce@momjian.us>

View thread
From: Bruce Momjian <bruce@momjian.us>
To: Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, Peter Eisentraut <peter_e@gmx.net>, Andrew Dunstan <andrew@dunslane.net>, Magnus Hagander <magnus@hagander.net>, Tom Lane <tgl@sss.pgh.pa.us>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2012-09-11T21:13:35Z
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, Sep 11, 2012 at 08:27:49AM +0200, Stefan Kaltenbrunner wrote:
> On 09/10/2012 05:19 PM, Bruce Momjian wrote:
> > On Mon, Sep 10, 2012 at 12:06:18PM -0300, Alvaro Herrera wrote:
> >>> It is this kind of run-around that caused me to generate my own doc
> >>> build in the past;  maybe I need to return to doing my own doc build.
> >>
> >> You keep threatening with that.  You are free, of course, to do anything
> >> you want, and no one will break sweat about it.  I already said I will
> >> work on getting this up and running, but I can't give you a deadline for
> >> when it'll be working.
> > 
> > My point is that this frequent doc build feature was removed with no
> > discussion, and adding it seems to be some herculean job that requires
> > red tape only a government worker would love.
> 
> Not sure how you got that impression - but understand all requirements
> to something is usually key to implementing a solution, so discussing
> those requirements seems like a sensible thing to do.
> sysadmin is a volunteer effort and we do our best to deal with both
> keeping the existing infrastructure up and improving as we can but
> resources are limited and we need to consider the time/effort ration of
> stuff.
> Anyway alvaro clearly stated he would deal with it but obviously
> thatthat is not enough for your urgent demands so there is really not
> much we can do about it...

Don't know about "urgent", but I made this request in May:

	http://archives.postgresql.org/pgsql-hackers/2012-05/msg00480.php

and at a certain point, waiting four months and discussing it repeatedly
just isn't an efficient use of my time.

It only took me 15 minutes to implement.  I am guessing the complexity
of the Postgres infrastructure just makes the job much harder to
implement there.  

This is a good example of why some organizations like cloud services,
where they can host things without waiting for the item to get to the
top of the IT TODO list.

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

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