| From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
|---|---|
| To: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
| Cc: | Patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: GIN improvements |
| Date: | 2008-06-06 14:16:38 |
| Message-ID: | 484946C6.1080807@sigaev.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
> How about having a constant sized "fastupdate" buffer, of say 100 rows
> or a fixed number of pages, and when that becomes full, the next
> inserter will have to pay the price of updating the index and flushing
I'm not sure that is acceptable because flushing pending list may take several
seconds in unpredictable moment.
> the buffer. To keep that overhead out of the main codepath, we could
> make autovacuum to flush the buffers periodically.
Do you mean that GIN sends a "smoke signal" to the autovacuum launcher process
to ask about vacuum?
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2008-06-06 14:29:14 | Re: Overhauling GUCS |
| Previous Message | Heikki Linnakangas | 2008-06-06 14:02:23 | Re: GIN improvements |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2008-06-06 22:36:57 | Re: partial header cleanup |
| Previous Message | Heikki Linnakangas | 2008-06-06 14:02:23 | Re: GIN improvements |