| From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
|---|---|
| To: | Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com> |
| Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, Simon Riggs <simon(at)2ndQuadrant(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Pluggable Indexes |
| Date: | 2009-01-22 10:10:39 |
| Message-ID: | 4978461F.3030308@sigaev.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> What other constraints are there on such non-in-core indexex? Early (2005)
> GIST indexes were very painful in production environments because vacuuming
> them held locks for a *long* time (IIRC, an hour or so on my database) on
> the indexes locking out queries. Was that just a shortcoming of the
> implementation, or was it a side-effect of them not supporting recoverability.
GiST concurrent algorithm is based on Log Sequence Number of WAL and that was
the reason to implement WAL (and recoverability) first in GiST.
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2009-01-22 11:39:07 | Re: Pluggable Indexes (was Re: rmgr hooks (v2)) |
| Previous Message | Magnus Hagander | 2009-01-22 10:10:05 | Re: Re: [COMMITTERS] pgsql: Explicitly bind gettext() to the UTF8 locale when in use. |