Horton

Re: Draft release notes complete

Andrew Dunstan <andrew@dunslane.net>

View thread
From: Andrew Dunstan <andrew@dunslane.net>
To: Bruce Momjian <bruce@momjian.us>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, Tom Lane <tgl@sss.pgh.pa.us>, Peter Eisentraut <peter_e@gmx.net>, Magnus Hagander <magnus@hagander.net>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2012-09-06T01:33: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 09/05/2012 09:25 PM, Bruce Momjian wrote:
> On Wed, Sep  5, 2012 at 09:56:32PM -0300, Alvaro Herrera wrote:
>> Excerpts from Tom Lane's message of mié sep 05 20:24:08 -0300 2012:
>>> Andrew Dunstan <andrew@dunslane.net> writes:
>>>> The only reason there is a significant delay is that the administrators
>>>> have chosen not to run the process more than once every 4 hours. That's
>>>> a choice not dictated by the process they are using, but by other
>>>> considerations concerning the machine it's being run on. Since I am not
>>>> one of the admins and don't really want to take responsibility for it I
>>>> am not going to second guess them. On the very rare occasions when I
>>>> absolutely have to have the totally up to date docs I build them myself
>>>> - it takes about 60 seconds on my modest hardware.
>>> I think the argument for having a quick docs build service is not about
>>> the time needed, but the need to have all the appropriate tools
>>> installed.  While I can understand that argument for J Random Hacker,
>>> I'm mystified why Bruce doesn't seem to have bothered to get a working
>>> SGML toolset installed.  It's not like editing the docs is a one-shot
>>> task for him.
>> As far as I understand, Bruce's concern is not about seeing the docs
>> built himself, but having an HTML copy published somewhere that he can
>> point people to, after applying some patch.  To me, that's a perfectly
>> legitimate reason to want to have them quickly.
> Correct.  I have always had a working SGML toolset.  If we are not going
> to have the developer site run more often, I will just go back to
> setting up my own public doc build, like I used to do.  I removed mine
> when the official one was more current/reliable --- if that has changed,
> I will return to my old setup, and publish my own URL for users to
> verify doc changes.

How often do you want? After all, 
<http://developer.postgresql.org/docs/postgres/index.html> is presumably 
going to keep pointing to where it now points.

cheers

andrew