| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Cc: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org, Pavan Deolasee <pavan(dot)deolasee(at)enterprisedb(dot)com>, Nikhil S <nikhil(dot)sontakke(at)enterprisedb(dot)com> |
| Subject: | Re: HOT for PostgreSQL 8.3 |
| Date: | 2007-02-09 15:17:14 |
| Message-ID: | 24850.1171034234@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Teodor Sigaev <teodor(at)sigaev(dot)ru> writes:
>> Implementing the "replace these TIDs" operation atomically would be
>> simple, except for the new bitmap index am. It should be possible there
> That isn't simple (may be, even possible) from GIN.
I suspect that those pushing this idea only care about btrees anyway,
so one possible answer is that HOT is only possible when the table has
only btree indexes --- or at least, only indexes of AMs that support the
replace-these-TIDs operation. (Yet another pg_am flag...)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2007-02-09 15:45:44 | possible TODOs |
| Previous Message | Teodor Sigaev | 2007-02-09 15:12:03 | Re: HOT for PostgreSQL 8.3 |