Re: HOT for PostgreSQL 8.3
| От | Pavan Deolasee |
|---|---|
| Тема | Re: HOT for PostgreSQL 8.3 |
| Дата | |
| Msg-id | 2e78013d0702160811y436df049t1ade9e465dcd2778@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: HOT for PostgreSQL 8.3 ("Zeugswetter Andreas ADI SD" <ZeugswetterA@spardat.at>) |
| Ответы |
Re: HOT for PostgreSQL 8.3
|
| Список | pgsql-hackers |
On 2/16/07, Zeugswetter Andreas ADI SD <ZeugswetterA@spardat.at> wrote:
> > As described, you've made
> > that problem worse because you're trying to say we don't know which
of
> > the chain entries is pointed at.
>
> There should be a flag, say HOT_CHAIN_ENTRY for the tuple the
it's called HEAP_UPDATE_ROOT
Just to avoid any confusion with the patch I sent out this week, we are
setting HEAP_UPDATE_ROOT on all tuples which are HOT-updated.
We set HEAP_ONLY_TUPLE for all tuples which does not have index
reference. So may be combination of (HEAP_UPDATE_ROOT & ~HEAP_ONLY_TUPLE)
can be used to identify index referred tuple in a HOT-update chain.
Thanks,
Pavan
--
EnterpriseDB http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: