Re: index-only scans
Kevin Grittner <kevin.grittner@wicourts.gov>
From: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
To: <postgres@cybertec.at>,"Robert Haas" <robertmhaas@gmail.com>
Cc: "Heikki Linnakangas" <heikki.linnakangas@enterprisedb.com>, <pgsql-hackers@postgresql.org>
Date: 2011-08-12T21:39:26Z
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 →
-
Reduce the alignment requirement of type "name" from int to char, and arrange
- 5f6f840e93a3 8.4.0 cited
Robert Haas <robertmhaas@gmail.com> wrote: > That's one of the points I asked for feedback on in my original > email. "How should the costing be done?" It seems pretty clear that there should be some cost adjustment. If you can't get good numbers somehow on what fraction of the heap accesses will be needed, I would suggest using a magic number based on the assumption that half the heap access otherwise necessary will be done. It wouldn't be the worst magic number in the planner. Of course, real numbers are always better if you can get them. -Kevin