| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Davis <pgsql(at)j-davis(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: GIN fast insert |
| Date: | 2009-02-26 16:44:16 |
| Message-ID: | 603c8f070902260844h4456ceefh5667a407acd741b1@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Feb 26, 2009 at 11:41 AM, Teodor Sigaev <teodor(at)sigaev(dot)ru> wrote:
>> it be? So far we've ruled out using the planner to prevent index
>> scans when the pending list is long (because it's not reliable) and
>> cleaning up the pending list during insert when needed (because it
>> won't work with Hot Standby). We haven't decided what WILL work,
>
> During insert it will work with Hot Standby because there is no any
> limitation for number of pages touched or WAL records. There is a problem
> with cleanup invoked by gingettuple - slave could not start cleanup process
> at all and hence it could emit an error if tidbitmap becomes lossy.
I didn't think about that option - might be reasonable.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2009-02-26 16:48:59 | Re: Synchronous replication & Hot standby patches |
| Previous Message | Teodor Sigaev | 2009-02-26 16:41:42 | Re: GIN fast insert |