| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Teodor Sigaev <teodor(at)sigaev(dot)ru>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: GIN fast insert |
| Date: | 2009-02-20 07:10:09 |
| Message-ID: | 499E5751.1050405@enterprisedb.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas wrote:
> On Thu, Feb 19, 2009 at 8:36 AM, Teodor Sigaev <teodor(at)sigaev(dot)ru> wrote:
>>> handle it is not terribly efficient, oh well. The one thing that
>>> concerns me is - what will happen in a hot standby environment, when
>>> that patch is committed? In that situation, I believe that we can't
>>> call modify any heap or index pages, so...
>> I don't see a problems here, because indexes in postgres don't depend on any
>> transaction's ids or modes as heap depends. WAL-logger works without that
>> knowledge too. May be I missed something here or don't understand.
>>
>> Although heap's pages could be changed by setting commit-status bits on
>> tuple even in read-only transaction, but that changes are not WAL-logged.
>> That is correct for index's page too.
>
> It would be helpful if Heikki or Simon could jump in here, but my
> understanding is that cleaning up the pending list is a read-write
> operation. I don't think we can do that on a hot standby server.
Right, can't do that on a hot standby server.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ITAGAKI Takahiro | 2009-02-20 08:48:44 | Re: Allow on/off as input texts for boolean. |
| Previous Message | Andrew Dunstan | 2009-02-20 04:09:09 | Re: ORDER BY with EXCEPT? |