| From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCHES] GIN improvements |
| Date: | 2009-02-11 14:53:36 |
| Message-ID: | 4992E670.5010507@sigaev.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
> But the real bottom line is: if autovacuum is working properly, it
> should clean up the index before the list ever gets to the point where
> it'd be sane to turn off indexscans. So I don't see why we need to hack
> the planner for this at all. If any hacking is needed, it should be
> in the direction of making sure autovacuum puts sufficient priority
> on this task.
Autovacuum will start if table has GIN index with fastupdate=on and number of
inserted tuple since last vacuum > autovacuum_vacuum_threshold.
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2009-02-11 15:02:07 | Re: GIN fast insert |
| Previous Message | Tom Lane | 2009-02-11 14:50:34 | Re: Re: [COMMITTERS] pgsql: Update autovacuum to use reloptions instead of a system catalog, |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2009-06-24 15:27:02 | Re: BUG #2401: spinlocks not available on amd64 |
| Previous Message | Tom Lane | 2009-02-09 19:54:05 | Re: [PATCHES] GIN improvements |