Re: SSI patch version 14

Поиск
Список
Период
Сортировка
Искать
От
Kevin Grittner
Тема
Re: SSI patch version 14
Дата
Msg-id
4D46B9D4020000250003A043@gw.wicourts.gov
Ответ на
Список
Дерево обсуждения
Re: SSI patch version 14 "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: SSI patch version 14 "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: SSI patch version 14 Dan Ports <drkp@csail.mit.edu>
Re: SSI patch version 14 Dan Ports <drkp@csail.mit.edu>
Re: SSI patch version 14 Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Re: SSI patch version 14 "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: SSI patch version 14 "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: SSI patch version 14 Dan Ports <drkp@csail.mit.edu>
Re: SSI patch version 14 "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: SSI patch version 14 Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Re: SSI patch version 14 Andrew Dunstan <andrew@dunslane.net>
Re: SSI patch version 14 Robert Haas <robertmhaas@gmail.com>
Re: SSI patch version 14 Dan Ports <drkp@csail.mit.edu>
Re: SSI patch version 14 David Fetter <david@fetter.org>
Re: SSI patch version 14 Markus Wanner <markus@bluegap.ch>
Re: SSI patch version 14 Robert Haas <robertmhaas@gmail.com>
Re: SSI patch version 14 Markus Wanner <markus@bluegap.ch>
Re: SSI patch version 14 Robert Haas <robertmhaas@gmail.com>
Re: SSI patch version 14 "A.M." <agentm@themactionfaction.com>
Re: SSI patch version 14 Robert Haas <robertmhaas@gmail.com>
Re: SSI patch version 14 Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Re: SSI patch version 14 "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Jeff Davis  wrote:
> On Mon, 2011-01-31 at 07:26 -0600, Kevin Grittner wrote:
>>> And why are you reading the infomask directly? Do the existing
>>> visibility functions not suffice?
>>  
>> It's possible we re-invented some code somewhere, but I'm not
>> clear on what code from this patch might use what existing
>> function. Could you provide specifics?
> 
> In CheckForSerializableConflictOut(), it takes a boolean "valid".
Ah, now I see what you're talking about.  Take a look at where that
"valid" flag come from -- the CheckForSerializableConflictOut are
all place right after calls to HeapTupleSatisfiesVisibility.  The
"valid" value is what HeapTupleSatisfiesVisibility returned.  Is it
possible that the hint bits will not be accurate right after that? 
With that in mind, do you still see a problem with how things are
currently done?
-Kevin

В списке pgsql-hackers по дате отправления
От: Andrew Dunstan
Дата:
От: Simon Riggs
Дата:
FAQ