Re: Draft release notes complete
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
From: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
To: Jeff Janes <jeff.janes@gmail.com>
Cc: Bruce Momjian <bruce@momjian.us>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2012-05-16T19:49:25Z
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 16.05.2012 22:38, Jeff Janes wrote: > For item: > Improve COPY performance by adding tuples to the heap in batches > (Heikki Linnakangas) > > I think we should point out that the batching only applies for COPY > into unindexed tables. Nice as the feature is, that is pretty big > limitation not to mention. No, it applies to indexed tables too. However, if there are indexes on the table, the overhead of updating the indexes will probably make any speedup in the heap insertions look tiny in comparison. The optimization doesn't apply if the table has BEFORE or INSTEAD OF triggers, or volatile DEFAULT expressions need to be evaluated. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com