| From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: GIN fast insert |
| Date: | 2009-02-13 15:47:22 |
| Message-ID: | 4995960A.7080708@sigaev.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> [ shrug... ] The proposed implementation fails to be particularly
> fast-start anyway, since it will process the entire pending queue
> before returning anything to the executor.
That is not true for fastupdate=off. But in any case it could be improved, but
improvements doesn't solve the issue with lossy bitmap.
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-02-13 15:47:44 | Re: composite types DROP..CASCADE behaviour - bug or intentional? |
| Previous Message | Tom Lane | 2009-02-13 15:41:44 | Re: GIN fast insert |