Re: Draft release notes complete
Alexander Korotkov <aekorotkov@gmail.com>
From: Alexander Korotkov <aekorotkov@gmail.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2012-05-22T21:38:06Z
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 →
-
Expose track_iotiming information via pg_stat_statements.
- 5b4f34661143 9.2.0 cited
-
Rewrite GiST support code for rangetypes.
- 80da9e68fdd7 9.2.0 cited
-
Clean up a couple of box gist helper functions.
- d50e1251946a 9.2.0 cited
-
Replace the "New Linear" GiST split algorithm for boxes and points with a
- 7f3bd86843e5 9.2.0 cited
On Wed, May 23, 2012 at 1:26 AM, Bruce Momjian <bruce@momjian.us> wrote: > On Thu, May 10, 2012 at 10:22:58PM +0400, Alexander Korotkov wrote: > > "Improve GiST box and point index performance by producing better trees > with > > less memory allocation overhead (Alexander Korotkov, Heikki Linnakangas, > Kevin > > Grittner)" > > Is this note about following two commits? > > http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h= > > 7f3bd86843e5aad84585a57d3f6b80db3c609916 > > http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h= > > d50e1251946a6e59092f0a84fc903532eb599a4f > > These improvements influence not only boxes and points but all > geometrical > > datatypes. > > OK, new wording: > > Improve GiST geometric type index performance by producing better > trees with less memory allocation overhead (Alexander Korotkov) Thanks! Also, I've some notes about removing reviewers. "Improve GiST index build times (Alexander Korotkov)" I think Heikki Linnakangas should be also listed as author of that patch because he didn't only review and commit, but actually put his hands on code. Isn't my authorship of this patch lost now? http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=80da9e68fdd70b796b3a7de3821589513596c0f7 I think earlier this patch was taken into account in entry "Add support for range data types". Probably, we need separate entry for this patch? ------ With best regards, Alexander Korotkov.