Horton

Re: Draft release notes complete

Tom Lane <tgl@sss.pgh.pa.us>

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

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.

			regards, tom lane