Re: GiST insert algorithm rewrite
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>, Teodor Sigaev <teodor@sigaev.ru>, Oleg Bartunov <oleg@sai.msu.su>
Date: 2010-11-16T20:46:15Z
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 →
-
New feature:
- 0ad7db4be4b1 7.1.1 cited
Robert Haas <robertmhaas@gmail.com> writes: > Oh. So do the indexes just degrade over time until they eventually > need to be REINDEX'd? At some point you might reach a state where a reindex would be helpful. But the same is true of btrees. I don't think this is a serious objection, at least not unless backed by evidence that the tree often degrades rapidly. Anyway fixing it would be material for a different patch. regards, tom lane