Re: Inlining comparators as a performance optimisation
Bruce Momjian <bruce@momjian.us>
From: Bruce Momjian <bruce@momjian.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Greg Stark <stark@mit.edu>, Peter Geoghegan <peter@2ndquadrant.com>, Tom Lane <tgl@sss.pgh.pa.us>, Andrew Dunstan <andrew@dunslane.net>, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, PG Hackers <pgsql-hackers@postgresql.org>
Date: 2011-10-05T15:31:57Z
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 →
-
Speed up conversion of signed integers to C strings.
- 4fc115b2e981 9.1.0 cited
-
Remove some unnecessary tests of pgstat_track_counts.
- f4d242ef9473 9.1.0 cited
-
Remove cvs keywords from all files.
- 9f2e21138693 9.1.0 cited
-
Code cleanup for function prototypes: change two K&R-style prototypes
- b9954fbb4ef2 8.3.0 cited
-
Use Min() instead of min() in qsort, for consistency and to avoid
- b38900c76776 8.2.0 cited
-
pgindent run for 8.2.
- f99a569a2ee3 8.2.0 cited
-
Switch over to using our own qsort() all the time, as has been proposed
- 6edd2b4a91bd 8.2.0 cited
Robert Haas wrote: > Markus Wanner took a crack at generalizing the autovacuum machinery > that we have now into something that could be used to fire up > general-purpose worker processes, but it fell down mostly because I > (and, I think, others) weren't convinced that imessages were something > we wanted to suck into core, and Markus reasonably enough wasn't > interested in rewriting it to do something that wouldn't really help > his work with Postgres-R. I'm not sure where Bruce is getting his > timeline from, but I think the limiting factor is not so much that we > don't have people who can write the code as that those people are > busy, and this is a big project. But you can bet that if it gets to > the top of Tom's priority list (just for example) we'll see some > motion...! I was thinking of setting up a team to map out some strategies and get community buy-in, and then we could attack each issue. I got the 2-3 years from the Win32 timeline. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +