| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Marc Mamin <M(dot)Mamin(at)intershop(dot)de> |
| Cc: | "'pgsql-performance(at)postgresql(dot)org'" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: gin performance issue. |
| Date: | 2016-02-05 15:07:17 |
| Message-ID: | 12466.1454684837@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Marc Mamin <M(dot)Mamin(at)intershop(dot)de> writes:
> http://explain.depesz.com/s/wKv7
> Postgres Version 9.3.10 (Linux)
> Hello,
> this is a large daily table that only get bulk inserts (200-400 /days) with no update.
> After rebuilding the whole table, the Bitmap Index Scan on r_20160204_ix_toprid falls under 1 second (from 800)
> Fastupdate is using the default, but autovacuum is disabled on that table which contains 30 Mio rows.
Pre-9.5, it's a pretty bad idea to disable autovacuum on a GIN index,
because then the "pending list" only gets flushed when it exceeds
work_mem. (Obviously, using a large work_mem setting makes this worse.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Filip Rembiałkowski | 2016-02-05 15:33:28 | Re: bad COPY performance with NOTIFY in a trigger |
| Previous Message | Filip Rembiałkowski | 2016-02-05 12:45:10 | Re: bad COPY performance with NOTIFY in a trigger |