Horton

Re: Draft release notes complete

Andrew Dunstan <andrew@dunslane.net>

View thread
From: Andrew Dunstan <andrew@dunslane.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <bruce@momjian.us>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2012-05-10T10:43:17Z
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 05/10/2012 01:29 AM, Tom Lane wrote:
> Bruce Momjian<bruce@momjian.us>  writes:
>> The docs finally built 90 minutes after my commit, and the URL above is
>> now working.  (Does it always take this long to update?)
> I believe the new implementation of that stuff is that the devel docs
> are built whenever the buildfarm member guaibasaurus runs for HEAD,
> which it seems to do on an hourly schedule.  This is definitely not as
> fast-responding as Peter's former custom script, but I'm not sure if
> it's worth thinking of another way.
>

I don't see any reason it can't run more frequently, though. Currently a 
run takes 15 minutes or so. We could reduce that by making it skip some 
steps, and get it down to about 10 minutes. It would be perfectly 
reasonable to run every 5 minutes (it won't schedule concurrent runs - 
if the lock file is held by another run it exits gracefully). Of course, 
that's up to Magnus and Stefan.

cheers

andrew