Re: [pgsql-patches] Ctid chain following enhancement
| От | Zdenek Kotala |
|---|---|
| Тема | Re: [pgsql-patches] Ctid chain following enhancement |
| Дата | |
| Msg-id | 465C30CF.5080105@sun.com обсуждение исходный текст |
| Ответ на | Re: Ctid chain following enhancement ("Pavan Deolasee" <pavan.deolasee@gmail.com>) |
| Ответы |
Re: [pgsql-patches] Ctid chain following enhancement
|
| Список | pgsql-patches |
Pavan Deolasee wrote:
>
> On 1/28/07, *Tom Lane* <tgl@sss.pgh.pa.us <mailto:tgl@sss.pgh.pa.us>>
> wrote:
>
> OTOH it might be
> cleaner to refactor things that way, if we were going to apply this.
>
>
> Here is a revised patch which includes refactoring of
> heap_get_latest_tid(), as per Tom's suggestion.
>
I'm looking on your patch. I have one comment:
If you have old tid and new tid you can easy compare if new tid points
to different page? And if page is still same there is no reason to
Unlock it and lock again. I think add inner loop something like:
Readbufer
Lock
do{
...
} while(ctid.block_id == tid.block_id)
ReleaseAndUnlock
can save some extra locking/unlocking cycle. What do you think?
Zdenek
В списке pgsql-patches по дате отправления: