| From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Index use during Hot Standby |
| Date: | 2008-10-20 15:47:28 |
| Message-ID: | 48FCA810.5030402@sigaev.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> One more thing about GiST - when database is switched from recovery mode to the
>> normal mode then it's needed to complete insertion in GiST and, possibly, vacuum
>> index. Dig around GistBulkDeleteResult->needFullVacuum and gistContinueInsert()
>
> OK, will look at those. (Problems++).
Not a very big issue: in this case index is still in workable state but not very
effective until vacuum it.
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2008-10-20 16:12:34 | Re: Block level concurrency during recovery |
| Previous Message | Hitoshi Harada | 2008-10-20 15:41:57 | Re: Window Functions: buffering strategy |